Closed
Bug 1476942
Opened 7 years ago
Closed 7 years ago
'Aa' button in reader mode jumps around when scrolling up/down
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1465618
People
(Reporter: sflorean, Unassigned)
References
Details
(Keywords: regression)
Environment:
Device: Nokia 6(Android 7.1.1), Samsung Galaxy S8 (Android 8.0);
Build: Nightly 63.0a1 (2018-07-19);
Steps to reproduce:
1. Add a page to the reading list;
2. Scroll up and down the content of the page;
3. Pay attention to 'Aa' option.
Expected result:
Scroll down - "Aa" option not displayed.
Scroll up - "Aa" option displayed.
Actual result:
"Aa" option continues to appear/dissapear at the bottom of the page when we scroll down. Same behavior when the page is scrolled up.
Video: https://drive.google.com/open?id=1ZWcJctLAm6v7OLUdpsneomPERbfbbSML
Updated•7 years ago
|
Component: Reader View → Panning and Zooming
Keywords: regression,
regressionwindow-wanted
Product: Firefox for Android → Core
Hardware: ARM → All
Summary: Visual effects for the 'Aa' option when a page in reading mode is scrolled up/down → 'Aa' button in reader mode jumps around when scrolling up/down
Version: Firefox 63 → 63 Branch
| Reporter | ||
Comment 1•7 years ago
|
||
Regression window (autoland):
Last good build: 1fafb8e0
First bad build: 403ba3d9
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1fafb8e07051ccf79a2fa5364d334baa7ac83f10&tochange=403ba3d9539a35562eae14061b9fcb1c80d0860a
Keywords: regressionwindow-wanted
Comment 2•7 years ago
|
||
Respectively it seems like bug 1465618 should handle this:
(Botond Ballo [:botond] wrote in bug 1465616 comment #44)
> This patch is known to regress the behaviour of fixed elements during async
> scrolling (after a repaint things should be fine).
>
> The regression should be short-lived and will be fixed by bug 1465618 soon.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(kmadan)
Resolution: --- → DUPLICATE
Comment 4•7 years ago
|
||
Fixed in 63 in bug 1465616.
You need to log in
before you can comment on or make changes to this bug.
Description
•