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

Firefox 4: Can't escape embedded objects using moveToParentTreeInterceptor script #1429

Closed
nvaccessAuto opened this issue Mar 23, 2011 · 4 comments
Closed

Firefox 4: Can't escape embedded objects using moveToParentTreeInterceptor script #1429

nvaccessAuto opened this issue Mar 23, 2011 · 4 comments
Labels
bug feature/browse-mode MozillaWork
Milestone
2011.1.1

Comments

@nvaccessAuto
Copy link

Reported by jteh on 2011-03-23 22:57
Str:

  1. In Firefox 4, visit a site containing an embedded object such as the NVDA web site.
  2. Move to and press enter on the embedded object.
  3. Press NVDA+control+space to get out of it.
  4. Expected: Focus should be returned to the document.
  5. Actual: Nothing.

The problem is that in Firefox 4, there is no separate document window. Previously, the document window was the parent of the embedded object window, so moving up the hierarchy eventually landed in the document. Now, you land on the top level Firefox frame.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2011-03-28 07:16
Changes:
Milestone changed from 2011.2 to 2011.1.1

@nvaccessAuto
Copy link
Author

Comment 2 by mdcurran on 2011-03-29 03:07
Fixed in d5b4d42, however only tested with Flash so far. Can be closed if we can get an answer on Java.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2011-03-29 05:19
Java is a bit strange and doesn't seem to use a !GeckoPluginWindow at all. Unfortunately, this means this fix won't work for Java (and I'm not even sure we can fix it).

The good news is that I tried this with a browser embedded Adobe Reader document and it does work very nicely there.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2011-03-30 20:59
Note that the solution we implemented here was very much a hack. The correct solution is to get this fixed in Firefox. See MozillaBug:646360.

@nvaccessAuto nvaccessAuto added this to the 2011.1.1 milestone Nov 10, 2015
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 MozillaWork
Projects
None yet
Milestone
2011.1.1
Development

No branches or pull requests
1 participant
@nvaccessAuto