Closed
Bug 1084187
Opened 11 years ago
Closed 11 years ago
Tapping the Home button scrolls browser frames to the top
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: fabrice, Unassigned)
Details
STR:
1. Open a web page from a home screen bookmark.
2. Scroll down.
3. Tap on the Home button
4. Re-open the same page from the home screen.
Expected:
The page is still at the same scroll position.
Observered:
The page has been scrolled to the top.
Comment 1•11 years ago
|
||
Unable to reproduce on master. Possibly a race?
| Reporter | ||
Comment 2•11 years ago
|
||
Seems fixed in this morning OTA. I suspect this was also a regression of bug 989198.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Comment 3•11 years ago
|
||
I'm pretty sure that this is caused by bug 989198. ;)
After bug 989198 is landed, all key events are propogating to both system app and the foreground app. That's why the web page is scrolled to the top.
Tzu-Lin is working on bug 1014418. Home keys and Volumes keys should be perserved by System app. No application is allowed to override the behaviour. So, after bug 1014418 is landed, no Home keys is dispatched to the foreground app, and this bug should be fixed.
Comment 4•11 years ago
|
||
(In reply to Gina Yeh [:gyeh] [:ginayeh] from comment #3)
> Tzu-Lin is working on bug 1014418. Home keys and Volumes keys should be
> perserved by System app. No application is allowed to override the
> behaviour. So, after bug 1014418 is landed, no Home keys is dispatched to
> the foreground app, and this bug should be fixed.
In the meantime when bug 1014418 is getting reviewed, we will have a quick fix in System app to avoid home key being dispatched to applications. The quick fix will unblock bug 989198's landing.
Comment 5•11 years ago
|
||
This is the quick fix mentioned in comment 4: bug 1091353
You need to log in
before you can comment on or make changes to this bug.
Description
•