Closed Bug 1401519 Opened 7 years ago Closed 4 years ago

[Activity Stream] - Top Sites area is still scrollable after reaching the end of a pannel

Categories

(Firefox for Android Graveyard :: Activity Stream, defect, P5)

57 Branch
ARM
Android
defect

Tracking

(fennec-, firefox57 affected)

RESOLVED INCOMPLETE
Tracking Status
fennec - ---
firefox57 --- affected

People

(Reporter: bsurd, Unassigned)

References

Details

(Whiteboard: [MobileAS])

Steps to reproduce: 1. Open Fennec; 2. In Top Sites have more than 8 sites in order to enable scrolling; 3. Fast swipe left or right in the Top Sites section of the tab. Expected result: If the first or second panel of the Top Sites is displayed the user can't scroll any longer in that section and the entire page is scrolled Actual result: The Top Sites area is still scrollable. Video: https://goo.gl/PMRpSk
This only affects users who scroll really fast through top sites and it's already a P5.
tracking-fennec: ? → -
All open Activity Stream bugs are moving from the whiteboard tag, "[mobileAS]", to the Firefox for Android component, "Activity Stream", so that I can keep better track of these bugs as the new triage owner; I will send out an email shortly with additional details, caveats, etc.
Component: Theme and Visual Design → Activity Stream
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.