Support programmatic edit key commands
- introduce a scoped setter which enables the keyboard during spoken feedback's lifetime - remove restriction/message from ChromeVox disclaimer asking user to enable a11y vk - re-map some Search-like-function keys 1. Search+Left/Right -> Home/End 2. Search+Shift+Left/Right -> Shift Home/End 3. Search+Ctrl+Left/Right -> Ctrl+Home/End 4. Search+Shift+Ctrl+Left/Right -> Shift+Ctrl+Home/End - re-map braille commands to edit key commands as follows: 1. dot 3/6 chord -> previous/nextCharacter -> Left/Right 2. dot 2/5 chord -> previous/nextWord -> Ctrl+Left/Right 3. dot 1/4 chord -> previous/nextObject -> Up/Down 4. dot 2-3/5-6 chord -> previous/nextGroup -> Ctrl+Up/Down (jumpToTop/Bottom remain dots 1-2-3/4-5-6 and trigger ordinary edit key command mappings). notes: we use the vk codepath because it handles compatibility down the stack for us and potentially triggers other side effects such as auto complete/IME Test: with a braille display, ensure a11y vk off. Press incrementally Ctrl + t; verify new tab shows up. In Google Docs, press Search+Left/Right (and all other combos enumerated above). Verify proper caret/selection afterwards. Turn on sticky mode. Verify Search nav performs ChromeVox commands rather than send keys. Do all of the same with a braille display inside of Docs. Verify ability to edit and navigate directly from display. Bug: Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I4878c8a930cd643c406294b7f302c9ad2c07ee9f Reviewed-on: https://chromium-review.googlesource.com/823578 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#524545}
Showing
Please register or sign in to comment