- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Chromium API
Chromium API is a browser automation input method based on Devtools protocol and it provides many benefits when automating a Chromium-based browser.
It can be used with the following Modern activities:
- Use Application/Browser
- Click
- Type Into
- Hover
-
Note: This method only works on web elements. It doesn't work on elements that are not part of the webpage, such as pop-ups.
Here are some insights you might want to consider when designing browser automation with the ChromiumAPI input method.
Reliability
Sending keys/mouse input via hardware events means sending them to the operating system’s mouse/keyboard input stream. From there, the events are forwarded to the target application, the browser in our case, which parses them and sends them further to the web pages.
Sending keys/mouse input via ChromiumAPI means sending them directly to the browser. Therefore, this input method eliminates a communication channel that can fail (as any other communication channel).
Directly communicating with the browser via this new method means fewer communication channels, and thus improved automation reliability.
Works in the background
Hardware events need the elements to be on the screen, focused, in the foreground. ChromiumAPI does not have this requirement as it works while the browser is minimized and another tab is focused (mind that the modern activities tend to activate the working tab).
Improved efficiency
The ChromiumAPI sends trusted events triggers, which are the exact chain of events triggered when a human does the same action. This means that, besides the automation that worked with Simulate, a lot more is available now through ChromiumAPI.
Other benefits
It allows sending hotkeys directly to the browser.
The Clear before typing property is natural with this method, since it does not empty the target element field by default.
The Click with modifiers actions are more efficient and reliable.
When the browser is started with ChromiumAPI, a ribbon shows up stating that the browser started in debug mode (highlighted below in blue). This message does not show up if the extension is installed via policy.
