Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: hover text only working when VO enabled #26183

Merged
merged 2 commits into from Oct 29, 2020
Merged

Conversation

codebytere
Copy link
Member

Description of Change

Closes #25695.

Previously some screenreader-associated accessibility tooling was being enabled exclusively when VoiceOver was turned on, which broke Hover Text among some other things. This is because we only called ax_state->OnScreenReaderDetected(); if VoiceOver was enabled, and is fixed by removing that condition. The previous condition seems to have been added as a result of atom/atom#3288, but some local testing seems to ensure that text to speech still works after this removal.

cc @ckerr @jkleinsc @zcbenz

Checklist

Release Notes

Notes: Fixed an issue where Hover Text on macOS Catalina did not work without VoiceOver also being enabled.

@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Oct 27, 2020
Copy link
Member

@ckerr ckerr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this behavior was introduced by 6bc59cf and one of the comments for that patch says

This looks like something has changed in Chrome. With the VoiceOver patch, I mimicked Chrome's behavior of enabling the accessibility tree when VoiceOver was active, and disabling the tree when inactive.

This comment is 5 years old so it's likely stale information, but just to check -- did you confirm that we're still tracking to how Chrome behaves wrt the accessibility tree?

Copy link
Member

@ckerr ckerr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Other than the addition of AXManualAccessibility, this matches what chrome_browser_application_mac.mm is doing.

@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Oct 28, 2020
@codebytere
Copy link
Member Author

not ok 1330 webContents module render view deleted events does not emit current-render-view-deleted when speculative RVHs are deleted and nativeWindowOpen is set to true
  TypeError: Cannot read property 'webContents' of undefined
      at Timeout._onTimeout (electron\spec-main\api-web-contents-spec.ts:1213:21)
      at listOnTimeout (internal/timers.js:554:17)
      at processTimers (internal/timers.js:497:7)

failure is unrelated, merging.

@codebytere codebytere merged commit 7949402 into master Oct 29, 2020
@release-clerk
Copy link

release-clerk bot commented Oct 29, 2020

Release Notes Persisted

Fixed an issue where Hover Text on macOS Catalina did not work without VoiceOver also being enabled.

@trop
Copy link
Contributor

trop bot commented Oct 29, 2020

I have automatically backported this PR to "9-x-y", please check out #26244

@trop trop bot removed the target/9-x-y label Oct 29, 2020
@trop
Copy link
Contributor

trop bot commented Oct 29, 2020

I have automatically backported this PR to "10-x-y", please check out #26245

@trop
Copy link
Contributor

trop bot commented Oct 29, 2020

I have automatically backported this PR to "11-x-y", please check out #26246

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Electron apps based are not accessible via MacOS "Hover Text" unless Voice Over is turned on
3 participants