📘

Note:

The UiPath Extension for Edge can only be installed on Windows 10 versions 1803 and above.

Interactive Selection Fails After Installing the Extension

When Edge is opened, corresponding background processes are also created and remain active even after the browser is closed. After the extension is installed and the browser is closed, the Edge process is still running in the background and does not get updated with the new information to be able to generate selectors in Edge.

Before you create your first automation projects for Edge, you must close the browser and terminate the corresponding process from Task Manager after you install the extension.

Starting a Job From Orchestrator Fails

On Windows logon, the Edge browser automatically starts as a background process. The extensions page is also loaded in the background, but is closed after several seconds. However, the extensions page is not reloaded when Edge is booted up, making extensions unusable.

There are two methods to deal with this situation:

• Restart the Edge browser.
• Set a default browser other than Edge.

The "htmlWindowName" Attribute is Not Validated

Selectors which contain the htmlWindowName attribute can not be validated. This is caused by a Windows known issue.

Selectors Are Not Generated For Local Web Pages

If your process uses local web pages (files stored on the local machine) in Edge, selectors are not generated for any element on those pages. This is caused by a Windows known issue.

Imprecise Actions Performed by Type Activities

In particular cases, the Type Into, Type Secure Text, and Send Hotkey activities erroneously interact with their target elements. To prevent this, you need to enable the ClickBeforeTyping property.

As a general rule for browser automations, it is also recommended to enable the SimulateClick property for activities which perform click operations.