The fix for this problem will be shipped with Firefox 112. Some WebDriver clients like Selenium that use the Chrome DevTools Protocol (CDP)īy default for logging events could trigger a hang in Firefox's experimental CDP Potential hang with moz:debuggerAddress capability set to true:Īfter enabling the site-isolation feature in Firefox with geckodriver 0.32.1 Removed the unknown path error which is not part of the WebDriver specification. The Firefox version check has been extended to enable the execution of distributions with custom prefixes for the application name.

This behavior resulted in a malfunction due to a regression in Firefox, particularly affecting the Firefox 121 release. While searching for a default Firefox installation on the system, geckodriver used the Contents/MacOS/firefox-bin executable instead of the binary specified in the app bundle's ist file. Updated dependencies (base64, clap, rust-url) Specifying -port=0 as an argument allows geckodriver to dynamically find and use an available free port on the system. The error handling has undergone refactoring, now utilizing the anyhow and thiserror crates. Support for using a page range as integer for the Print command. Geckodriver supports all available commands: This functionality encompasses a range of methods, including passwords, Virtual Authenticators serve as a WebDriver Extension designed to simulate user authentication (WebAuthn) on web applications during automated testing. Workarounds are listed in the geckodriver This can affect access to the generated profile directory, which may result Shipped with Ubuntu 22.04), it may see a different filesystem to the host.

When Firefox is packaged inside a container (like the default Firefox browser

Startup hang with Firefox running in a container (e.g.

Free downloads Mozilla Firefox 120.0