In the UiPath Platform, the Webdriver protocol introduces support for headless browser automations. This means that browser automations don't necessarily have to rely on visual elements on screen, such as window frames. Automations are executed in the background, without you having to keep up the browser window. Nonetheless, the Webdriver protocol is not strictly meant for headless browser automations, and can also be used to operate browsers visually.
Automation projects with the Webdriver protocol can only be created for Chrome and Firefox.
Automations via the Webdriver protocol do not require you to install corresponding browser extensions.
Although the Webdriver protocol can be used for both headless and visual browser automations, it is not meant to replace the UiPath browser extensions, giving you the freedom to use whichever option suits you best.
Selectors generated by the Webdriver protocol are the same as those generated by the UiPath browser extensions. This applies for both headless and visual browser automations.
The Webdriver opens a new browser session (process) every time, which is independent of any other browser session. When the browser is closed, the corresponding webdriver application (
geckodriver.exe) is also terminated along with all the associated browser sessions.
Currently, the Webdriver protocol supports the following actions:
- Execute browser activities inside an Open Browser container. This works for both headless and visual browser automations.
- Execute browser activities outside an Open Browser container. This works for both headless and visual browser automations.
- Full support for interactive selection and generating native selectors. This only works for visual browser automations.
Updated about a month ago