Closed
Bug 1408620
Opened 7 years ago
Closed 4 years ago
"Speak selected text when the key is pressed" (TTS) feature of OSX no longer works in Firefox 57
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
RESOLVED
DUPLICATE
of bug 1226473
Tracking | Status | |
---|---|---|
firefox57 | --- | fix-optional |
firefox58 | --- | fix-optional |
People
(Reporter: john.luke.greco, Unassigned)
Details
(Keywords: regression, Whiteboard: [mac2020_2])
Attachments
(1 file)
64.28 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171013042429 Steps to reproduce: Enable 'Speak selected text' in OS X: - System Preferences -> Speech and Dictation -> Text to Speech, - Enable 'Speak selected text when key is pressed' with an appropriate shortcut key. I use Control+Space Select text on a webpage, press Ctrl+Space (or the appropriate shortcut) !!!Select different text, and press the same shortcut a second time!!! Actual results: The first time, only the selected text is spoken. The second and subsequent times, the selected text is not spoken. Instead the title of every tab is spoken, then the entire contents of the webpage are spoken. Expected results: The first time, only the selected text is spoken. The second and subsequent times, only the selected text is spoken.
Reporter | ||
Updated•7 years ago
|
Updated•7 years ago
|
status-firefox57:
--- → affected
Updated•7 years ago
|
Component: Disability Access → Disability Access APIs
Product: Firefox → Core
Updated•7 years ago
|
Flags: needinfo?(dbolter)
Comment 1•7 years ago
|
||
We need to know when this regressed.
Flags: needinfo?(dbolter)
Keywords: regressionwindow-wanted
Reporter | ||
Comment 2•7 years ago
|
||
I tried to narrow this down with mozregression and hit a few snags which might be illuminating: On Nightly builds from 2016-04-06 to 2017-09-08, trying to use the select-to-speak feature will cause a dialog to appear warning that "Accessibility support is partially disabled due to incompatibility with new nightly features". Sometimes this warning is spoken instead of the selected text. (Clicking "learn more" on this dialog takes me to: https://support.mozilla.org/en-US/kb/accessibility-and-ppt?as=u&utm_source=inproduct "Accessibility not available during multi-process support") Beginning on 2017-09-08 14:51:15.213000, revision 0b442d470556cd39f407c3395b006764b3038bf0, this warning dialog no longer appears. However the functionality is still broken. Bisecting results were all over the place: 2015-10-28 good 2015-11-08 good 2015-11-14 good 2015-11-15 bad 2015-11-16 bad 2015-11-17 bad 2015-11-19 bad 2016-01-26 bad 2016-02-29 bad 2016-03-17 bad 2016-03-26 bad 2016-03-28 bad 2016-03-30 bad 2016-03-31 bad 2016-04-01 bad 2016-04-02 good 2016-04-03 good 2016-04-05 good ---- Warning message STARTS appearing here --- 2016-04-06 bad 2016-04-08 bad 2016-04-09 good (worked despite warning) 2016-04-12 tested 6 times. 3 times it worked despite warning, 3 times it failed. 2016-04-14 bad 2016-04-15 good (worked despite warning) 2016-04-16 bad 2016-04-17 bad 2016-04-18 bad 2016-04-20 bad .... 2017-09-08 bad ---- Warning message STOPS appearing here --- 2017-09-09 bad ... (I haven't found a working version after this) Taking a wild stab in the dark: the warning message connects this functionality to multi-process support. The 2016-04-12 Nightly seemed to work 50% of the time. Some sort of race condition? However! On my normal install of Firefox 55.0.3 the feature works without trouble every time. (Could this be because I'm using legacy extensions that would cause multi-process support to be disabled?)
Comment 3•7 years ago
|
||
It's a recent regression, and it'd be good to give it some priority. I'm curious though if that's indeed a right component, and a11y is involved here. Can we have a list of primary suspects?
Comment 4•7 years ago
|
||
My understanding is that we've never officially supported accessibility on OSX. David, can you help triage? Not sure what the priority should be here.
Flags: needinfo?(dbolter)
Comment 5•7 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #4) > My understanding is that we've never officially supported accessibility on > OSX. David, can you help triage? Not sure what the priority should be here. We don't officially support to the level we would recommend Firefox to VoiceOver users (unfortunately), but we haven't actively prevented use. I think the case here is that multi-process has regressed this use case. It will be hard to prioritize fixing this given current priorities unfortunately. Perhaps it is something simple though, and it just needs someone to debug.
Flags: needinfo?(dbolter)
Updated•7 years ago
|
Updated•6 years ago
|
Keywords: regressionwindow-wanted
Updated•4 years ago
|
Whiteboard: [mac2020_2]
Updated•4 years ago
|
Severity: normal → S3
Updated•4 years ago
|
Priority: P3 → P1
Comment 6•4 years ago
|
||
Slack had a similar issue but fixed it in a recent release.
Comment 7•4 years ago
|
||
Closing as a dup of an older bug with the same issue.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•