Issue metadata
Sign in to add a comment
|
ChromeVox shouldn't read invisible unicode chars |
||||||||||||||||||||||||
Issue descriptionChrome Version: 68.0.3410.0 OS: ChromeOS What steps will reproduce the problem? 1. Activate ChromeVox (Ctrl + Alt + Z). 2. Have an element with content: "" (zero width white space) e.g.: <button>  </button>. 3. Navigate to the element. What is the expected result? It should read the same as "no content" like an empty button: <button></button> What happens instead? ChromeVox reads "zero width no break space..." Bug affecting ChromeOS File Manager: crbug.com/835789
,
Aug 1
,
Aug 1
The assigned owner "elkurin@google.com" is not able to receive e-mails, please re-triage. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 9
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by yawano@chromium.org
, Jul 31Labels: cvox-starter-bug