Open Bug 1067366 Opened 10 years ago Updated 2 years ago

Horizontal scrolling stops after several pixels

Categories

(Core :: Layout, defect)

35 Branch
x86
macOS
defect

Tracking

()

UNCONFIRMED

People

(Reporter: barnaby, Unassigned)

Details

(Keywords: steps-wanted)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20140915030204

Steps to reproduce:

Scrolling sideways on https://shrewdness.waterpigs.co.uk/test/?url=https%3A%2F%2Faaronparecki.com to move other columns into view


Actual results:

The container scrolls a couple of pixels before stopping, regardless of actual scroll gesture length or inertia. Additionally, trying to scroll to the left (content moving to the right) triggers the browser “back” behaviour after fingers removed from the trackpad, even when the content is not completely scrolled to the right.


Expected results:

The container should scroll as usual, and the browser back behaviour should only be triggered when scrolling content to the right (left-moving gesture) over an x-scrollable container which is already scrolled completely in that direction.
Can reproduce. As a workaround, I'm able to scroll horizontally using the touchpad gesture by moving my fingers slightly in the opposite direction, then scrolling as normal. 

This seems to be caused by a conflict with the back/forward gestures. IMO those gestures should only trigger when the page is scrolled fully in that direction, should only be triggerable when there is a page in history to go back/forward to, and should provide some sort of feedback (like Chrome's arrows or Safari's "sliding" animation) when they are about to be triggered.
Component: Untriaged → Layout
Product: Firefox → Core
I can't reproduce this, on Mac.  What are the exact steps to reproduce?  What exact gestures are being performed, using how many fingers?  I'm using two fingers, dragging left or right to scroll, fwiw.
Flags: needinfo?(barnaby)
(In reply to Scott Odle from comment #1)
> Can reproduce. As a workaround, I'm able to scroll horizontally using the
> touchpad gesture by moving my fingers slightly in the opposite direction,
> then scrolling as normal. 
> 
> This seems to be caused by a conflict with the back/forward gestures. IMO
> those gestures should only trigger when the page is scrolled fully in that
> direction, should only be triggerable when there is a page in history to go
> back/forward to, and should provide some sort of feedback (like Chrome's
> arrows or Safari's "sliding" animation) when they are about to be triggered.

Please use the tracking request form and provide justification when requesting tracking. Until this can be verified I will not be tracking.
As per comment 3, no tracking flags needed unless this can be reliably reproduced.
Hello guys,

So I tried to reproduce this issue both on a Mac OS X 10.9, with Firefox/35.0 and on a macOS High Sierra 10.13 with the same version of the browser.

I have also tried with the latest FF 61.0b4 build on the same machines with no success. 

The trackpad is highly responsive and scrolls exactly for how much the motion is made on it with the fingers when side scrolling.

Multiple websites where tested that contained content that could be side scrolled(https://webdesignledger.com/horizontal-scrolling-sites-youll-love/), alongside with zooming in the contents of the pages in such a manner in which the side-scroll bar is displayed.

The page provided in the bug's description is no longer available. 

Are there any other steps or elements that we should take into consideration when reproducing this issue?
Flags: needinfo?(sjodle)
Keywords: qawanted
Severity: normal → S3

Clear needinfos that are pending on inactive users.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(sjodle)
Flags: needinfo?(barnaby)
You need to log in before you can comment on or make changes to this bug.