Chromevox stops reading abruptly
Reported by
apa...@bluejeansnet.com,
Feb 22 2017
|
|||||||||||
Issue description
Chrome Version : 56.0.2924.87
OS Version: OS X 10.10.5
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
BACKGROUND
This issue manifests itself when the user tries to navigate from one button to another. There are two buttons:
i. buttonOne: focusing on this button triggers a tooltip next to it. Tabbing out of this button closes said tooltip.
ii. buttonTwo: this button follows button two in the tabbing order.
What steps will reproduce the problem?
1. Tab to buttonOne
2. Now tab to buttonTwo.
What is the expected result?
Chromevox reads the aria-label for buttonOne in step 1.
Chromevox reads the aria-label for buttonTwo in step 2.
What happens instead of that?
Chromevox reads the aria-label for buttonOne in step 1.
It only reads the first part of the aria-label in step 2. e.g. if the aria-label is "moderator settings", chromevox only reads "mod".
Please provide any additional information below. Attach a screenshot if
possible.
Potential cause: jquery-ui uses buttonOne's attributes to store information about the triggered tooltip. Removal of these attributes on tabbing out causes chromevox to stop reading. This functionality was working fine on Chrome 55. It also works correctly using voiceover with chrome 56.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
,
Feb 23 2017
Tested in chrome # 56.0.2924.87 and # 58.0.3020.0 on Mac 10.12.3 and not able to reproduce the issue.Please find the screen cast for your reference. @ apatil: Could you please let me know if i have missed anything and if possible, provide us with a sample URL of the issue which would help us to triage the issue further. Thanks in Advance.
,
Feb 23 2017
@rbasuvula: It's difficult for me to provide access to the exact page where this issue is observed but I can provide some more details. The issue is caused by a line 5818 in jquery-1.8.2.js [elem.parentNode.removeChild( elem )]. This line triggers cvox.ChromeVoxEventWatcher.visibilityChangeWatcher [chromeVoxChromePageScript.js:1903 NOT pretty printed]. I hope this information was helpful. Thanks for your help!
,
Feb 23 2017
^some more details that I forgot: On chrome 55, elem.parentNode.removeChild( elem ) does not trigger this visibiltyChangeWatcher
,
Mar 1 2017
Thank you for providing feedback. removing "Needs-Feedback" label.
,
Mar 6 2017
All ChromeVox bugs should be OS:Chrome by default. We can remove in the rare case where it's not.
,
Mar 6 2017
,
Mar 20 2017
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Apr 23 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 28 2018
Closing for now as it's been open for a year. If this is still an issue, feel free to reopen. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by kapishnikov@chromium.org
, Feb 22 2017