Preserve all meaningful space between inlines even if neighbor is focusable
After this should be better for Braille output, easier to predict for speech, and more accurately represents the format. For example 2 links on separate lines of HTML source will have a whitespace node between them -- this is rendered on the screen but until this CL did not show up in the a11y tree. It also corrects the word boundary algorithm so that the start of a word does not occur in a whitespace-only node. ChromeVox's move-by-word algorithm was adjusted to be able to find the next node when the current one did not have a word stop. Bug: None Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I4f7aa1624a2b5f7efb3d957656ec0b11fcc2a9af Reviewed-on: https://chromium-review.googlesource.com/657561Reviewed-by:David Tseng <dtseng@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#501625}
Showing
Please register or sign in to comment