Ruby Error Handling
How to work around errors caused by axe DevTools Ruby 4.3
Version 4.3.0 and above of the axe DevTools integrations use a new technique when analyzing a page, which opens a new window at the end of a run. Many of the issues outlined in this document address common problems with this technique and their potential solutions.
An example error message for this problem will include a message about
switchToWindow. For example:
(node:17566) UnhandledPromiseRejectionWarning: Error: Malformed type for "handle" parameter of command switchToWindow
Popup blockers prevent us from opening a new window when analyzing a page. The default configuration for most automation testing libraries should allow popups. Please make sure that you do not explicitly enable popup blockers which may cause an issue while running the tests.
If for some reason you are unable to analyze a page without errors, axe provides a new chainable method that allows you to run the legacy procedure. When using this method axe excludes accessibility issues that may occur in cross-domain frames and iframes.
Axe::Configuration.legacy_mode is deprecated and will be removed in v5.0. Please report any errors you may have while analyzing a page so that they can be fixed before the legacy version is removed.
webdriver = open_page
Axe::Configuration.instance.legacy_mode = true
results = analyze_page