[Proton] [Microsoft Office] The elastic overscroll effect is shaking in Reading View at the bottom and top of word documents
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
People
(Reporter: tbabos, Unassigned)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [mac:ux] [proton-platform])
*Affected Versions:
Nightly 89.0a1
Tested On:
MacOS 10.15, MacOS 11 (M1)
Steps to reproduce:
- Log in to Office 365
- Open any created Word document
- Select View -> Reading view
- Fast swipe to the bottom or top of the document
Expected Results:
The elastic overscroll effect should not happen in Reading View (Safari behavior)
The animation should be smooth.
Actual Results:
The overscroll effect is shaking upon scrolling to the bottom or top of the document using fast swipe gestures. (magic mouse or touchpad). Recording at: https://drive.google.com/file/d/1yvXF_OplrA0VRSA8lIiKOTARtSu9Tiw3/view?usp=sharing
Notes:
Please note that even with the overscroll feature disabled, there will be a slight shake at the bottom of the page the very first time when the document was loaded in Reading View.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Looks like there are scroll and dommousescroll event handlers on the scrollable div container, not sure what they do, source if minified. So they could be involved.
Safari overscrolls in editing mode, but not reader mode. Chrome does not overscroll in either mode.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
•
|
||
I am seeing the same script what I found in bug 1705699 comment 12 on the scroll event handler on #WACContainer element. But in this case disabling the event listener doesn't make this issue reproducible.
Reporter | ||
Comment 3•4 years ago
|
||
Please note that this also causes the content on the pages to shake, recording: https://drive.google.com/file/d/1MhXOKuUoLUKBT-JHu0nZ91pMcRb8QFp1/view?usp=sharing
Comment 4•4 years ago
|
||
I'd say this will also be fixed by the webcompat intervention for bug 1705699.
Comment 5•4 years ago
|
||
Marking this as Resolved > Worksforme since this was resolved by the intervention for bug 1705699.
Description
•