Closed
Bug 1317130
Opened 8 years ago
Closed 8 years ago
While scrolling a gmail email, if the mouse pointer is in the far right section, then scrolling is janky
Categories
(Core :: Panning and Zooming, defect, P3)
Core
Panning and Zooming
Tracking
()
RESOLVED
INVALID
People
(Reporter: mayankleoboy1, Unassigned)
Details
(Whiteboard: [gfx-noted])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20161112030203
Steps to reproduce:
1. Open a new profile
2. Log into your gmail account. Open a mail that is atleast long enough to scroll a few page downs worth.
3. Click the mouse pointer in the far right section of the gmail page, as shown in the pic attached. Let the mouse pointer be there.
4. Scroll with the touchpad
Actual results:
When the mouse is in the right section, the scrolling of the mail is not smooth. It ends abruptly. There is no jank, but scrolling feels weird.
Compare this with clicking the mouse pointer inside the body of the mail, and then scrolling.
Expected results:
same scrolling.
This reproduced with layers.async-pan-zoom.enabled set to either true/false.
Reporter | ||
Comment 2•8 years ago
|
||
Reporter | ||
Updated•8 years ago
|
Component: General → Panning and Zooming
![]() |
||
Comment 3•8 years ago
|
||
I can reproduce if split pane mode = No or Horizontal in my case(because my monitor is not wide).
On Chrome, the scroll amount on the right side empty area of message pane is bigger than the scroll amount on body area.
On Firefox38, Nightly52.0a1, the scroll amount on the right side empty area is smaller than the scroll amount on body area.
It seems the page implements its own scroll method. So, I think this seems the site problem.
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [gfx-noted]
Comment 4•8 years ago
|
||
I can reproduce, and I agree with Alice that the page is implementing its own scroll method. There is a DOMMouseScroll listener on that right pane which is intercepting the wheel events and doing something with them.
This could moved to Tech Evangelism but considering the behaviour is different in Chrome as well it's unlikely the Gmail folks care enough to fix this. I'd rather not waste our Evangelism team's time on this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(bugmail)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•