Assigned
Status Update
No update yet.
Comments
vi...@google.com
removed the dup; this is possibly about how android spans work on empty strings.
- the calculation in the composable level seemed correct but the layout was not
- it happens for a new line as well
- one problem with both includeFontPadding true/false is that the cursor height is possibly can be visually improved to match the text ascent/descent rather than line top/bottom (might be challenging)
ae...@google.com
I do not fully understand your points, though I was wondering if a similar "trick" to measure "HHHHHHHHHHH" cannot be used here, because if I'm not mistaken the cursor gets drawn by text layout measuring on empty string.
Description
It would be nice to have these checks print out warnings instead (or be able to toggle between errors or warnings depending on how strict you want accessibility to be) so that all my tests don't fail if there is a view that doesn't have enough height. I know I can suppress these errors using the .setSuppressingResultMatcher() method, but this defeats the purpose of using the accessibility checks.
In short, I'd much prefer knowing if there is an accessibility issue that is then up to my discretion whether to fix it or not while still being able to pass my integration tests rather than have all my tests fail due to a native Switch not having enough height, for example.