How can I modify the "Asynchronous Pan/Zoom" field under "Graphics" in about:support?
Hello,
I have two versions of Firefox on my computer, a nightly build (version 51) and a standard Firefox (version 48). Whenever I bring up the about:support page in Firefox 48, the "Asynchronous Pan/Zoom" field under the "Graphics" category has a value of "none". However, in Firefox 51 Nightly, the same field has a value of "wheel input enabled; touch input enabled". Both Firefoxes use the same profile, so I don't that is what is causing the discrepancy. My question is how can adjust my Firefox 48 have the same value in the "Asynchronous Pan/Zoom" field (that is, "wheel input enabled; touch input enabled") like my Firefox 51 Nightly?
Soluzione scelta
Hi ideato,
Thank you for the guidance! Enabling E10s fixed the problem. Thank you for the help!
Leggere questa risposta nel contesto 👍 0Tutte le risposte (3)
Hello danielb5, i think it is not possible :-) to get the "Asynchronous Pan/Zoom" "wheel input enabled; touch input enabled" in 48.x like in Firefox 51.x Nightly
the Asynchronous Pan/Zoom is only enabled if you run Firefox with E10s enabled, maybe you have the
- layers.async-pan-zoom.enabled to true
- browser.tabs.remote.autostart to true (false in 48 by default)
but in 48 the E10s enabled is served to only 1% of qualified users (no extensions, no rtl-locales, accessibility mode not switched on, and touchscreens will not be selected in the first round, nor will users running Windows XP)
probably it is the cause that you can not see the "wheel input enabled; touch input enabled" in 48
i have the same as you in 48.x = "none", in beta 49.x and in developer 50.x i have only the = "wheel input enabled" and in nightly 51.x i have the same as you "wheel input enabled; touch input enabled".
now i DO NOT known if you create the
- browser.tabs.remote.force-enable to true (boolean pref)
(This is not encouraged, use it at your own risk!)
works, but i think not because the above..... "1% of qualified users (no extensions, no rtl-locales, accessibility mode....."
Definitely E10s needs more work : https://bugzilla.mozilla.org/show_bug.cgi?id=1299625 (please do not comment in bug reports)
thank you
Modificato da ideato il
Soluzione scelta
Hi ideato,
Thank you for the guidance! Enabling E10s fixed the problem. Thank you for the help!
You are welcome. :-)