Issue metadata
Sign in to add a comment
|
Select-to-Speak doesn't respect overflow:hidden |
||||||||||||||||||||||
Issue description
Example HTML:
<div style="width:200px;overflow:hidden">
<p style="width:400px">
A quick brown fox ran out to the cute and lazy cat.
</p>
</div>
Even though the end of the sentence is truncated visually, Select-to-Speak will read the whole thing.
,
Oct 31 2017
,
Nov 29 2017
,
Nov 30 2017
This is still a problem with text that overflows its boundaries on a single line, even though other overflow issues are fixed.
,
Nov 30 2017
,
Mar 8 2018
,
Mar 8 2018
This is a visual problem as well. Word highlight uses the automation API boundsForRange function, which returns an unclipped location. We need to either add a new function like boundsForRange that returns a clipped rect, or change boundsForRange to return a clipped rect. +dtseng, do you know if any part of Chromevox depends on boundsForRange, or do you have an opinion on whether it should be updated to return a clipped box or a new function should be added to Automation API?
,
Mar 19 2018
,
Sep 27
This bug is related to overflow and visibility. Select-to-Speak cannot determine when an element is visible or invisible if that is not reflected in the a11y tree. For example, a 1px by 1px element that is on the screen may be read whether or not it has overflow:hidden. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by katydek@google.com
, Oct 31 2017