New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for rich text editing in Google Chrome #2634
Comments
Comment 1 by jteh on 2012-10-15 04:00 Technical: Chrome isn't exposing IAccessibleText correctly on editable documents. |
Comment 2 by jteh on 2014-02-28 04:51 |
Comment 3 by jteh on 2015-10-14 04:41 #1668 implements support for rich text editing in Mozilla apps. Most of this should be usable as is in Chrome, but a few changes to our Chrome specific code will be needed. Also, while GoogleIssue:chromium:347859 has now been fixed in Canary, there are a few remaining issues that need to be fixed in Chrome before this will work correctly. |
Comment 4 by jteh on 2015-10-14 05:11 |
Comment 5 by jteh on 2015-10-14 05:11 |
Comment 6 by jteh on 2015-10-14 07:10 |
Comment 9 by James Teh <jamie@... on 2015-11-02 05:18 This requires Chrome 47 or later. |
Comment 10 by jteh on 2015-11-02 05:18 |
…owsers such as Google Docs with braille support enabled. This requires Chrome 47 or later. As part of this, unify common code for web browsers exposing IAccessible2 into a new ia2Web module and use it for Mozilla and Chromium. Fixes #2634.
Reported by ateu on 2012-09-01 23:57
Steps to reproduce:
Expected result: The edited content can be reviewed with arrow keys.
Actual result: When moving with arrow keys, NVDA just says "blank".
Note: I think only google chrome canary and google chrome dev switches to focus mode when tabbing to this fields.
The text was updated successfully, but these errors were encountered: