The edge save as button with new edge version

Help Activities
, ,
1

Hi all,
I found edge was upgrade from 131 to 133,
image
image
The save as button element was changed,

The image shows a comparison between download prompts in two versions of a web browser, with different user interface designs labeled as version 131 on the left and version 133 on the right. (由 AI 生成标题)
The image shows a comparison between download prompts in two versions of a web browser, with different user interface designs labeled as version 131 on the left and version 133 on the right. (由 AI 生成标题)594×209 30.5 KB

Is there currently a mature solution for clicking the save as button?
Is there an element that can select both old and new elements?

2

Hi @jmy , do you need to support the ‘Save As’ button for both the older and newer versions of edge? If so, you could just use the ‘Element Exists’ or ‘Check App State’ activity to first check which version of the save button has appeared, then just map the selector to each save button.

3

Hi @jmy

Use the “Check app state” activity to handle the situation. Identify the elements that are unique to the New Save As window. In cases where the element appears, use the Click activity to handle the new Save As window. If the element does not appear, use the previous Click activity that was used to handle the old Save As window.

Hope it helps!!

4

@jmy

indicate both and check what are the common attributes like innertext or aaname can be same …so use properties like those so that the selector works for both

if they are completely different then you might need to go with check app state with two different activities for each type of click

cheers

5

@jmy Use “Strict Selector” and “Fuzzy Selector” Together
UiPath Modern UI Automationallows you to configure both strict and fuzzy selectors.
Steps:

  1. Open the UI Explorer in UiPath.
  2. Select the “Save As” button in both versions of Edge.
  3. Check for differences in the selector attributes(e.g., aaname, class, ctrlname, title).
  4. Use wildcards (*) or variables to make the selector dynamic.
  5. Use Fuzzy Selector to allow UiPath to handle minor UI changes automatically.
    or Use a “Try-Catch” to Handle Both Versions