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

Reading using the mouse and Firefox 35.0 #4825

Closed
nvaccessAuto opened this issue Jan 18, 2015 · 7 comments
Closed

Reading using the mouse and Firefox 35.0 #4825

nvaccessAuto opened this issue Jan 18, 2015 · 7 comments

Comments

@nvaccessAuto
Copy link

Reported by dorinek on 2015-01-18 19:16
Hi.

After updating Firefox to version 3.5.0 NVDA does not read the objects using the mouse. ;The problem applies to eg. Google search results page.

Please solve this problem.

;Thank you.
Blocking #4833

@nvaccessAuto
Copy link
Author

Comment 1 by k_kolev1985 on 2015-01-18 20:09
Actually, it is Firefox 35.0 and not 3.5.0. But yes - I can confirm this. I'm running Firefox 35.0 with the latest "next" snapshot of NVDA on a Windows 8.1 64-bit machine. In my case, NVDA plays its error sound, probably due to the fact that it is a test version and the error sound is enabled for the test versions of NVDA.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2015-01-19 02:04
See also #3654, though this seems to be much worse now.

Technical: Mozilla have broken a couple of things here.

  1. On the Google Search results page, hit testing seems to be returning an object much higher in the heirarchy.
  2. Even with this wrong object, any unit other than character returns offsets of (0, 0). However, I don't think this issue is new; it just shows up because of issue 1.
    Issue 1 is the real problem.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2015-01-19 02:04
Changes:
Changed title from "Reading using the mouse and Firefox 3.5.0" to "Reading using the mouse and Firefox 35.0"

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2015-01-19 02:38
Filed MozillaBug:1123163.

@nvaccessAuto
Copy link
Author

Comment 5 by nvdakor on 2015-01-19 02:51
Hi,
People over at users mailing list speculate that somehow Firefox's way of handling CSS might be playing a role here. One user raised concerns that with more and more sites adopting CSS 3, it may pose a major issue.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2015-01-26 22:02
Fixed for Firefox 38. I've requested that the fix be uplifted to a sooner release, but that decision is up to Mozilla.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 8 by jteh on 2015-01-29 00:00
Okay. This got approved for Firefox 36 and 37 as well.

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

1 participant