Closed Bug 1233795 Opened 4 years ago Closed 4 years ago
First run in new profile on touchscreen has broken wheel scrolling
STR: 1. On a touchscreen windows device (I'm using a Surface with Windows 10 Pro), start Nightly with a new profile 2. Go to mozilla.org or any other website and try scrolling with an external mousewheel Expected: Page scrolls Actual: Page doesn't scroll. After closing and restarting the browser once the mousewheel works normally On the first boot into a new profile, about:support shows e10s is enabled and APZ is supporting mousewheel input. On the second boot, however, e10s is disabled. Based on what :jimm said this is because the touchscreen is detected as accessibility and so the code to disable e10s on accessibility kicks in. However it seems to do it late in startup, after e10s and APZ are enabled, leaving them in some sort of half-enabled state. Restarting the browser keeps e10s disabled right from the beginning and so everything works fine. According to :jimm I should also get a doorhanger about reduced accessibility support on the first start because of this, but I don't see that.
If I can reproduce I'll file a separate bug on the lack of a prompt for touch screens. Did you happen to check the console? I'm wondering if you see this message - http://mxr.mozilla.org/mozilla-central/source/browser/components/nsBrowserGlue.js#3333
I don't see that message either in the browser console or the web console. I also don't see it in stdout, but nothing shows up there anyway. I didn't try attaching Visual Studio to get the console output - that would probably happen too late anyway.
Hi Kats, I am unable to reproduce this on latest Aurora (46.0a2-20160207004019) and latest Nightly (47.0a1-20160207030402). External mouse scroll correctly works when I start Firefox with a new profile. Tested this on a Dell XPS 12 laptop (2in1) with the screen "detached" from keyboard. Is this still reproducible for you ? Maybe Surface tablet is a different environment than the Dell laptop and that's why I cannot reproduce it. However, related to the doorhanger you guys mention, I only got it once on both browser versions. Created a new profile after to test it again and it no longer appears. Also, regarding the about:support things, they work exactly as mentioned. First e10s and APZ for mouse scroll are enabled and after restart, e10s is disabled and "None" displayed for APZ. Thanks, Paul
I'm unable to reproduce the mousewheel brokenness on latest m-c. Resolving WFM.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.