Michael

Hey @jameelakowsar, As part of the `finishRun()` method we pass partial run in to a new window which should close after analyzing. When using `setLegacyMode()` it does not utilize `finishRun()`...

@jameelakowsar do you mind clarifying your question? WebDriverjs doesn't crawl, the expected additional time is just axe-core running with the test driver.

Closing as this is an enterprise feature

@somaalapati This is a dev task I don't think there is anything to QA

Closing added more error handling in CLI Ref: https://github.com/dequelabs/axe-core-npm/pull/555, https://github.com/dequelabs/axe-core-npm/pull/421, https://github.com/dequelabs/axe-core-npm/pull/681, https://github.com/dequelabs/axe-core-npm/pull/680 No QA required

Hey @moulinette, I ran lighthouse version 10.4.0 using chrome v117 which includes axe-core 4.7.2 and was unable to replicate the issue. I've also ran axe-core 4.8.1 directly on the page...

Hey @WillGibson do you mind providing some code example on what particular issue you are having? Are you running an e2e workflow where the domain consistently changes?

Hey @alicescfernandes just following up to see if this is still an issue.

Hey @jyurek just following up to see if this is still an issue with axe-core-gems 4.8.1

Hey @surgeboris I am currently taking a look at this and will provide an update when possible