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

Jump to bottom

NVDA doesn't work in the gmail.com login site from IE10 #3151

Closed
nvaccessAuto opened this issue Apr 14, 2013 · 4 comments
Closed

NVDA doesn't work in the gmail.com login site from IE10 #3151

nvaccessAuto opened this issue Apr 14, 2013 · 4 comments
Labels
bug feature/browse-mode
Milestone
2013.1

Comments

@nvaccessAuto
Copy link

Reported by k_kolev1985 on 2013-04-14 09:21
When opening www.gmail.com in Internet Explorer 10 with NVDA, it doesn't read the page. The current snapshot plays its error sound and the stable 2012.3.1 stays silent.

Steps to reproduce it:

  1. Open Internet Explorer 10 and go to www.gmail.com.
  2. Press the arrow keys to navigate around in the page.

Expected result: NVDA should read the page content.
Actual result: The stable NVDA 2012.3.1 stays silent and the current snapshot only plays its error sounds and doesn't speak anything.

I can invoke the dialog with the list of links (elements) with NVDA+F7, but when I try to activate a link by pressing Enter on it in the list, NVDA only gives an error and doesn't activate the link.

I've even launched IE with addons disabled (from Start -> Accessories -> System Tools), but that didn't improve the situation.

I'm attaching a log file from NVDA witch should contain the bug logged. The logging level was set to "Debugging" - hope it helps.
@nvaccessAuto
Copy link
Author

Attachment nvda-log-2013-04-14-k_kolev1985.txt added by k_kolev1985 on 2013-04-14 09:22
Description:

@nvaccessAuto
Copy link
Author

Comment 1 by Michael Curran <mick@... on 2013-04-28 11:52
In [ee8c7dc]:

Fix #3151 (browse mode does not work in IE 10 on www.gmail.com login page). When IE 10 is in standards mode document.getElementsByName nor getElementById will return a node given its MS unique ID. However, document.all.item(uniqueID) does work. So only in this special case (for now) if getElementsByName returns None (only happens in IE 10 standards mode) then try document.all.item(uniqueID), but catch _all_ exceptions around that line to make sure there are no surprizes introduced by this very specific fix. In long-term it would be good to move code to just use all.item all the time, but this of course is untested.

Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2013-04-28 22:52
Changes:
Milestone changed from None to 2013.1

@nvaccessAuto
Copy link
Author

Comment 3 by Brendon22 on 2013-05-02 07:45
Hello,
This has been fixed.

@nvaccessAuto nvaccessAuto added this to the 2013.1 milestone Nov 10, 2015
@nvaccessAuto nvaccessAuto mentioned this issue Nov 10, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug feature/browse-mode
Projects
None yet
Milestone
2013.1
Development

No branches or pull requests
1 participant
@nvaccessAuto