#54075: test: turn accessibility back off after the app a11y specs
Description of Change
Before: the app module > accessibility support functionality specs set a process-wide AXMode and the last one leaves nativeAPIs | webContents | inlineTextBoxes | extendedProperties on. On macOS and Windows every spec that runs after api-app-spec in the same shard therefore runs with renderer accessibility enabled. That is how a 43-x-y macos-arm64 / test (darwin, 2) run hit Chromium's DCHECK(GetAXTreeID().token()) in RenderFrameHostImpl::BindRenderAccessibilityHost ~950 tests later and SIGABRT'd the whole shard (job). Upstream keeps that as a DCHECK precisely because it still fires in the field (crbug.com/500881532, crbug.com/526541651).
After: accessibility is switched back off after each of those specs, so the rest of the suite runs with AXMode off as it does on Linux.
How: an afterEach in that describe block calling app.setAccessibilitySupportEnabled(false), which resets the scoped process mode set by either setter.
Checklist
- I have filled out the PR description
- I have reviewed and verified the changes
- tests are changed or added
Release Notes
Notes: none
Backports
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron