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

Closed
nvaccessAuto opened this Issue Sep 1, 2012 · 10 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Sep 1, 2012

Reported by ateu on 2012-09-01 23:57
Steps to reproduce:

  1. Open Google chrome and go to web mail pages, such as Hotmail or yahoo;
  2. Access the page to send an e-mail;
  3. Go to the field where the message is typed and edit something;

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.

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Oct 15, 2012

Comment 1 by jteh on 2012-10-15 04:00
This is an issue with Chrome. Accordingly, please file a bug against Chrome.

Technical: Chrome isn't exposing IAccessibleText correctly on editable documents.
Changes:
Added labels: invalid
State: closed

nvaccessAuto commented Oct 15, 2012

Comment 1 by jteh on 2012-10-15 04:00
This is an issue with Chrome. Accordingly, please file a bug against Chrome.

Technical: Chrome isn't exposing IAccessibleText correctly on editable documents.
Changes:
Added labels: invalid
State: closed

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Feb 28, 2014

Comment 2 by jteh on 2014-02-28 04:51
Filed GoogleIssue:chromium:347859.

nvaccessAuto commented Feb 28, 2014

Comment 2 by jteh on 2014-02-28 04:51
Filed GoogleIssue:chromium:347859.

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Oct 14, 2015

Comment 3 by jteh on 2015-10-14 04:41
Reopening this to deal with the remaining issues concerning rich text editing in Chrome.

#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.
Changes:
Removed labels: invalid
State: reopened

nvaccessAuto commented Oct 14, 2015

Comment 3 by jteh on 2015-10-14 04:41
Reopening this to deal with the remaining issues concerning rich text editing in Chrome.

#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.
Changes:
Removed labels: invalid
State: reopened

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Oct 14, 2015

Comment 4 by jteh on 2015-10-14 05:11
Filed GoogleIssue:chromium:542971.

nvaccessAuto commented Oct 14, 2015

Comment 4 by jteh on 2015-10-14 05:11
Filed GoogleIssue:chromium:542971.

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Oct 14, 2015

Comment 5 by jteh on 2015-10-14 05:11
Changes:
Changed title from "It's not possible review the edited content in Google chrome incide editable frames" to "Support for rich text editing in Google Chrome"

nvaccessAuto commented Oct 14, 2015

Comment 5 by jteh on 2015-10-14 05:11
Changes:
Changed title from "It's not possible review the edited content in Google chrome incide editable frames" to "Support for rich text editing in Google Chrome"

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Oct 14, 2015

Comment 6 by jteh on 2015-10-14 07:10
Filed GoogleIssue:chromium:542998 concerning tree flattening for role="textbox".

nvaccessAuto commented Oct 14, 2015

Comment 6 by jteh on 2015-10-14 07:10
Filed GoogleIssue:chromium:542998 concerning tree flattening for role="textbox".

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Oct 22, 2015

Comment 7 by James Teh <jamie@... on 2015-10-22 07:07
In commit b15f61e:
Merge branch 't2634' into next

Incubates #2634.
Changes:
Added labels: incubating

nvaccessAuto commented Oct 22, 2015

Comment 7 by James Teh <jamie@... on 2015-10-22 07:07
In commit b15f61e:
Merge branch 't2634' into next

Incubates #2634.
Changes:
Added labels: incubating

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Oct 23, 2015

Comment 8 by James Teh <jamie@... on 2015-10-23 04:32
In commit f42ae04:
Merge branch 't2634' into next

Incubates #2634.

nvaccessAuto commented Oct 23, 2015

Comment 8 by James Teh <jamie@... on 2015-10-23 04:32
In commit f42ae04:
Merge branch 't2634' into next

Incubates #2634.

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Nov 2, 2015

Comment 9 by James Teh <jamie@... on 2015-11-02 05:18
In commit a75357d:
Support for editing of rich text in Google Chrome and Chrome-based browsers 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.
Changes:
Removed labels: incubating
State: closed

nvaccessAuto commented Nov 2, 2015

Comment 9 by James Teh <jamie@... on 2015-11-02 05:18
In commit a75357d:
Support for editing of rich text in Google Chrome and Chrome-based browsers 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.
Changes:
Removed labels: incubating
State: closed

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Nov 2, 2015

Comment 10 by jteh on 2015-11-02 05:18
Changes:
Milestone changed from None to 2015.4

nvaccessAuto commented Nov 2, 2015

Comment 10 by jteh on 2015-11-02 05:18
Changes:
Milestone changed from None to 2015.4

@nvaccessAuto nvaccessAuto added this to the 2015.4 milestone Nov 10, 2015

jcsteh added a commit that referenced this issue Nov 23, 2015

Support for editing of rich text in Google Chrome and Chrome-based br…
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment