Closed Bug 773246 Opened 13 years ago Closed 12 years ago

Tabs Menu should have overscroll behavior only when full

Categories

(Firefox for Android Graveyard :: Toolbar, defect)

16 Branch
ARM
Android
defect
Not set
normal

Tracking

(firefox21 affected, fennec+)

RESOLVED WORKSFORME
Tracking Status
firefox21 --- affected
fennec + ---

People

(Reporter: paul.feher, Assigned: sriram)

Details

Nightly Fennec 16.0a1 (2012-07-11) Aurora Fennec 15.0a2 (2012-07-11) Device: Samsung Galaxy Tab OS: Android 3.1 Steps to reproduce: 1. Load any page. 2. open the tab menu. 3. Try to pan the opened tab. Expected: Panning shod not be possible only after the tab list is full. Actual: Panning is possible.
Whiteboard: [tablet]
Issue is also reproducible on Phones. Reproduced on Firefox Mobile 15.0b3 build 1 using a Samsung Galaxy R running Android 2.3.4
Summary: [TABLET] Panning in tab-menu shod not be possible only after the tab list is full → Panning in tab-menu shod not be possible only after the tab list is full
Whiteboard: [tablet]
Summary: Panning in tab-menu shod not be possible only after the tab list is full → Panning in tab-menu should not be possible only after the tab list is full
I'm confused about what this bug is.
Please see the video for more clarification. http://youtu.be/KOJcVZ1VTRU
tracking-fennec: --- → ?
Related to Bug 740281?
tracking-fennec: ? → +
Assignee: nobody → sriram
Summary: Panning in tab-menu should not be possible only after the tab list is full → Tabs Menu should have overscroll behavior only when full
(In reply to Cristian Nicolae (:xti) from comment #4) > Related to Bug 740281? Yes. This is Samsung's stock behavior.
Ian - Should we really be fighting these custom OEM behaviors? It's tiring and might not scale well as we run into more OEMs.
I'm fine to have a bounce here if that is Samsung's overscroll style. The only major issue I have with the video that Paul posted is that the tab rows get cut off along the bottom when you pull down, which really breaks the mental model of the "tray" layer in a weird way. If we can resolve that, I'm good.
Is this still valid? Please reopen, if so.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
I am still able to reproduce this on Firefox for Android 20.0b5 build 1(2013-03-13) and Firefox for Android 21.0a2(2013-03-14) using a Samsung Galaxy R(Android 2.3.4)
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Not reproducible on Firefox for Android 22.0a1(2013-03-14)
Closing based on comment 10. Please reopen if you can still reproduce.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.