User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140605174243 Steps to reproduce: Open FF 30.0 Go to any common site: nytimes.com Select any article and click to go to it. Swipe left (with two fingers) to return to front page Actual results: Nothing Expected results: FF 30.0 should have performed a 'back' operation. Clicking on the back arrow works correctly. The same steps on Chrome or Safari work correctly with the mouse swipes, backwards and forwards, eliminating the mouse as a problem.
Does it work if you swipe more slowly? Have you turned on swiping in the system preferences pane for the mouse?
Swiping has been turned on for a long, long time and worked well with FF upto about rev 29, then I started noticing flakey response to the swipes. It is intermittent and sometimes site specific. Swiping works most of the time in the yahoo email editor and never works when I am on the Amazon site. It seems that something is going on in the browsing engine that is site/html etc sensitive where FF misses or discards the swipe. Using the Back arrow always works.
Okay, just making sure we're not missing the obvious. Unfortunately I don't know what could be causing this. If you can find a way to reproduce this consistently, you can try finding a regression range, see https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Mozmill/How_to_do_regression_testing
Hi, I am unable to test this issue because I don't own an Apple Mighty Mouse for my iMac. Could you please try to reproduce this on the release(43.0.4) and/or the latest Nightly (https://nightly.mozilla.org/) and provide the results? When doing this, please try to reproduce with a new clean Firefox profile, maybe even in safe mode, as some of this issues may be caused by third party installed add-ons or custom settings(https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems). Thanks, Cipri
Since the reporter didn't provide the requested information, I will mark this issue as RESOLVED INCOMPLETE. If you still encounter this problem, please feel free to reopen this bug, or file a new one.