Blink should report reason for text changes to the accessibility tree |
||
Issue descriptionFor example, we want to know if a change to the contents or selection in a text box is due to: * Typing a character * Cut/copy/paste * Pressing keyboard shortcuts to move by word, extend selection, etc. * Clicking with the mouse * Programmatic change One option is that we could fire an AXEvent for each possible change. Events are bundled together, so we could associate changes to the tree with events that were probably responsible for those changes. This is most relevant for Mac & Chrome OS. On Mac, NSAccessibility requests the reason for changes to the accessibility tree, currently we just fake that info. On Chrome OS, ChromeVox could give more useful feedback if it knew the reason.
,
Dec 19 2017
,
Dec 20
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by dmazz...@chromium.org
, Dec 8 2017