Automate Google Chrome using native AutoHotkey.
How it works
Chrome offers a WebSocket based API they call the Chrome DevTools Protocol. This API is what allows web development tools to build integrations, and tools such as Selenium to perform their automation. The protocol's documentation describes a plethora of exciting endpoints accessible using this library, and can be found at the link below.
- No external dependencies such as Selenium are required
- Chrome can be automated even when running in headless mode
- Launching in headless mode is not currently supported by this library
- Chrome consistently benchmarks better than Internet Explorer
- Chrome offers extensions which provide unique opportunities for interaction
- Automate your Chromecast
- Connect to remote servers with FoxyProxy and update web based configs
- Manage your password vault with LastPass
- Many features are available that would be difficult to replicate in Internet Explorer
- Geolocation spoofing
- Chrome must be started in debug mode
- If chrome is already running out of debug mode, it must either be closed and reopened or launched again under a new profile that isn't already running
- You cannot attach to an existing non-debug session
- Less flexible than Internet Explorer's COM interface
- Cannot pass function references for callbacks
Using this Library
To start using this library you need to create an instance of the class . 's constructor accepts four optional parameters:
1. ProfilePath - This is the path, relative to the working directory, that your Chrome user profile is located. If an empty folder is given, chrome will generate a new user profile in it. When this parameter is omitted, Chrome will be launched under the default user profile. However, if chrome is already running under that user profile out of debug mode, this will fail. Because of this, it is recommended to always launch Chrome under an alternate user profile.
2. URL - The page that chrome should initially be opened to. Pass an empty string to open Chrome's homepage. When this parameter is omitted, Chrome will be opened to .
3. ChromePath - The path to find the Chrome executable file. When this parameter is omitted, Chrome will be launched from the path in its start menu entry.
4. DebugPort - The network port to communicate with Chrome over. When this parameter is omitted, port will be used as specified in the Chrome DevTools Protocol documentation.
Code: Select all