2

With the release of Firefox 52 this week, Windows 8 and 10 touchscreen users can now use e10s (provided they also have add-on support).

When I went into about:support today, I found that I was still disabled by an accessibility.

I have seen this question, which answers the basics of how to force enable e10s, but I would like to know if there is a way to tell what accessibility feature blocked my use of e10s.

6
  • I encountered a similar problem after I had used the Windows 10 touch keyboard in the Notification Area. After that, Firefox about:support showed that Multiprocess Windows was disabled due to an accessibility feature. Ultimately, I had to ensure that my Firefox Sync had a good copy of all my data and then delete/recreate my Firefox profile to alleviate the problem.
    – Run5k
    Mar 7 '17 at 20:13
  • 1
    Possible duplicate of How to check if multiprocess e10s option is enabled in your Firefox
    – Run5k
    Mar 7 '17 at 20:20
  • @Run5k I updated the question. I Know about that question (it helped me force-enable), but I would like to identify what specific accessibility features disabled e10s. I will look into the touch keyboard, but I don't think that is it. Mar 7 '17 at 23:34
  • IIRC, when I enabled the touch keyboard there was actually a message within Firefox that informed me of the change, but it has been quite a while. Even though I did know which accessibility feature disabled Multiprocess Windows, I still couldn't find a way to undo it. As I said, I finally just created a new Firefox profile and then Multiprocess Windows was enabled by default.
    – Run5k
    Mar 8 '17 at 1:21
  • @Run5k. Well I never got a warning, and the accessibility.loadedinlastsession flag is still reporting true, suggesting that it is something else. Mar 9 '17 at 2:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.