Closed
Bug 959686
Opened 12 years ago
Closed 12 years ago
[B2G] [Settings] Swiping to scroll the menu will move the scrollbar but not the menu options
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g-v1.2 unaffected, b2g-v1.3 affected)
RESOLVED
DUPLICATE
of bug 958549
Tracking | Status | |
---|---|---|
b2g-v1.2 | --- | unaffected |
b2g-v1.3 | --- | affected |
People
(Reporter: ckreinbring, Unassigned)
Details
(Whiteboard: burirun1.3-2)
Attachments
(2 files, 1 obsolete file)
Description:
The first time the user swipes the screen to scroll the Settings menu, the scrollbar will move but the menu options will remain at the top for a few seconds.
Repro Steps:
1) Update Buri to Build ID: 20140113004002
2) Make sure the "Enable APZ for all content" is enabled in the Developer menu.
3) Close the Settings window and tap Settings.
4) Swipe upward to scroll the menu down and observe the relationship between the scrollbar and the menu options.
Actual:
On the first swipe of the Settings menu the scrollbar will move but the menu options will not. After a few seconds the menu options will catch up to the scrollbar's position.
Expected:
The movement of the scrollbar and the menu options remain in sync.
Environmental Variables
Device: Buri 1.3 mozilla RIL
Build ID: 20140113004002
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/5bb1837de7c0
Gaia: b3fc4f712562ee92b0ed0bd17abc61be9a36a8da
Platform Version: 28.0a2
Firmware Version: V1.2-device.cfg
Notes:
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/cases/?filter-id=3680
See attached video clip and logcat logs
Reporter | ||
Comment 1•12 years ago
|
||
Reporter | ||
Comment 2•12 years ago
|
||
Issue does not occur on Buri 1.2 mozilla RIL due to the fact that APZ does not exist on 1.2
status-b2g-v1.2:
--- → unaffected
Reporter | ||
Comment 3•12 years ago
|
||
Attachment #8359872 -
Attachment is obsolete: true
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•