Dialog "Save as" no selector with Edge?

Help
1

When trying to download files from Edge I can not reach the “Save as” button, I always just get the underlying elements on the web page when indicating. Change of the UI Framework has no effect. Any solutions for this?

3 Likes
2

@moenk

have you installed Uipath Extension for the edge?

Thanks

1 Like
4

Well of course how else I’d get the underlying elements on the web page?

6

No worries
If we are using CLICK activity then make sure that SIMULATE CLICK is enabled
—and also the waitforready property as Complete in the property panel of click activity

Cheers @moenk

8

You know the difference between Internet Explorer and Edge? These are two different apps.

9

This does not work with Edge, did you tried that yourself?

10

Fine
Did you enable simulate click and tried once with click activity
Cheers @moenk

12

I dont want to click, I want to check if the element exists. But this was not the question: I need a valid selector for the “Save” button in Edge, as it can not be indicated.

13

Hmm
Fine
I would like to know what will be the next step once after we come to know that element exists
@moenk

15

I know this of course and it has nothing to do with Edge. Please note we are not talking about IE. Spying element on Edge is fine, but not the system dialogs.

16

@moenk
We are also facing same problem, since the Edge extension is experimental, we might face this issue.
Wait for the official release and currently use IE.

17

Try using Click Text activity.

18

Use delay activity to wait till pop up appears and after that use click image activity. Or click activity with simulate that will work.

19

Yes, this would be my next approach if UIPath fails to get a valid selector, third would be surface automation aka click image. The click text later would not work any more when I need to close the download dialog.

20

Great information, do you have planned timeline for that? Company GPO enforces the use of Edge, the project used to work fine with IE, but that is not an option any more.

21

No idea about the timeline. But below are links which speak about the known issues in Edge extension.

22

Hi Moenk, I ran into the same issue and I found a fix. When you use the ‘Indicate on screen’ to create a selector automatically, press F4 before click on the Save button. This will switch the UI Framework from Default to AA. Do not ask me what AA is but all I know is after changing this, you are able to select all the buttons you were not able to before. I understand my reply comes very late but maybe this will help someone else. Cheers.

7 Likes
23

Hello,
this answer is the correct solution.
Adding: AA stands for Active Accessibility and is one of the 3 UI Frameworks you can choose from in order to indicate elements. You can also find this setting in the UI Explorer Top Bar Button named ‘UI Frameworks’.
Regards

25

This solution works perfectly. Another thing to keep in mind is that it seems SimulateClick is not compatible with this window, but SendWindowMessages is.

Thanks a lot, I spent hours scratching my head over this one.

26

Hello, not sure if you managed to work it out or not. But for future reference/ people still facing any issue with save button, please use the following selector.

For some reason it works in one machine and another one either does not validate or pops the following error:
image

1 Like