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

Sometimes JAWS doesn't work in FF #90

Closed
jessegreenberg opened this issue Feb 21, 2018 · 7 comments
Closed

Sometimes JAWS doesn't work in FF #90

jessegreenberg opened this issue Feb 21, 2018 · 7 comments

Comments

@jessegreenberg
Copy link
Contributor

jessegreenberg commented Feb 21, 2018

From phetsims/resistance-in-a-wire#132 and phetsims/qa/issues/92.

Do these steps and most JAWS features do not work in any HTML web page.

  • Restart Computer
  • Enable JAWS
  • Enable Firefox

You can tab navigate, and JAWS will read focus, but virtual cursor and aria-live do not work. My gut says this is FF problem, so I am going to start with a bug report there.

@jessegreenberg
Copy link
Contributor Author

Hmm, maybe the problem is turning on Firefox while JAWS is still booting up.

@jessegreenberg
Copy link
Contributor Author

Hmm, perhaps the problem happens when turning on FF before JAWS fully boots up. I just waited for JAWS to be ready before opening FF and the problem wasn't there.

@jessegreenberg jessegreenberg self-assigned this Feb 21, 2018
@jessegreenberg
Copy link
Contributor Author

I verified that if I wait until JAWS is fully up and running, then open FF, everything sounds good. Ill report this as an issue to Mozilla

@jessegreenberg
Copy link
Contributor Author

Bug reported here: https://bugzilla.mozilla.org/show_bug.cgi?id=1440083

@jessegreenberg
Copy link
Contributor Author

Pinging @emily-phet and @terracoda so they are aware of this issue. I imagine this could easily happen during interviews or demonstrations, though JAWS users will likely be aware of the problem. As long as JAWS is fully up and running before Firefox is opened this problem shouldn't happen.

@jessegreenberg jessegreenberg removed their assignment Feb 21, 2018
@terracoda
Copy link
Contributor

@jessegreenberg, thanks for the ping. I will add this as a note in my interview prep documents.

@jessegreenberg
Copy link
Contributor Author

FF responded:

We know that this is a problem if you start JAWS after Firefox. The workaround
is to run JAWS before Firefox and let it finish loading (when it starts
speaking, it's done).

Note, too, that due to the E10S architecture, our window emulation code for
JAWS that is the culprit here has been changed to acommodate the multi-process
architecture and that JAWS 2018 (Version 19) is the only version supported
going forward, and that a lot of circumstances will have changed once we have
all the perf improvement and fixes for JAWS in place, currently slatted for
JAWS 60. So this bug may be obsoleted by then.

So it sounds like we will always have launch JAWS before FF, until FF Quantum broadly supports JAWS 19.

Pinging @terracoda, @emily-phet, and @phet-steele so they are aware. For future QA tests will will include this information in the issue. Closing.

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

2 participants