Skip to content
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

NVDA read all text while reading word by word, in an edit field under chrome #7372

Closed
abdullah5490 opened this issue Jul 10, 2017 · 5 comments

Comments

@abdullah5490
Copy link

After fixing the issue #6699 by adding #7201 in the master build, the NVDA is now navigating absolutely fine as character by character. but when I try to read word by word in an edit field under chrome, it read out all the content in that field, not each word one by one. For example, after typing this comment in the edit field using chrome, I pressed ctrl+right/left, it read my whole text written in this edit field. Not each word. This is only the case of chrome. in firefox, it just work fine.

@derekriemer
Copy link
Collaborator

@abdullah5490 commented on Jul 10, 2017, 4:57 PM MDT:

After fixing the issue #6699 by adding #7201 in the master build, the NVDA is now navigating absolutely fine as character by character. but when I try to read word by word in an edit field under chrome, it read out all the content in that field, not each word one by one. For example, after typing this comment in the edit field using chrome, I pressed ctrl+right/left, it read my whole text written in this edit field. Not each word. This is only the case of chrome. in firefox, it just work fine.

Which version of chrome?

@abdullah5490
Copy link
Author

@derekriemer its Version 59.0.3071.115 (Official Build) (64-bit). Language english.

@Adriani90
Copy link
Collaborator

@abdullah5490 I cannot reproduce this issue in Crhome 74. Are you still having this problem in NVDA 2019.1.1 in Crhome? If yes, is this issue happening in every edit field? Or only on example websites?

@abdullah5490
Copy link
Author

Hello there. no, this issue is now resolved, i'm testing it with chrome 74, and its working fine. you can now close this issue number.

@Adriani90
Copy link
Collaborator

Thanks for reporting back. Closing as works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants