A handful of browser tests began failing in Chrome 128+ (#1185), which the CI workflow began using recently.
The root cause appears to be a change in alert behavior when running automated tests: alerts are no longer shown, even when the BiDi Selenium driver is used.
Proposed solution
Pin Chrome to version 127 when running any browser tests. Follow up later with a fix or workaround.
Has this been tested?
[ ] 👍 yes, I added tests to the test suite
[ ] 💭 no, because this PR is a draft and still needs work
Context
A handful of browser tests began failing in Chrome 128+ (#1185), which the CI workflow began using recently.
The root cause appears to be a change in alert behavior when running automated tests: alerts are no longer shown, even when the BiDi Selenium driver is used.
Proposed solution
Pin Chrome to version 127 when running any browser tests. Follow up later with a fix or workaround.
Has this been tested?