Closed
Bug 1038642
Opened 10 years ago
Closed 6 years ago
[B2G] Navigating back often returns you to the top of the page
Categories
(Core :: DOM: Navigation, defect, P1)
Tracking
()
RESOLVED
WONTFIX
tracking-b2g | backlog |
People
(Reporter: pdol, Unassigned)
References
()
Details
(Whiteboard: [systemsfe][priority])
Device: Flame Build ID: 20140715000201 STR: 1) Open Browser 2) Navigate to reddit.com (or google.com) 3) Scroll down page 4) Click on a link to navigate to another page 5) After page starts to load, click back 6) Notice position on page Observed: User is returned to top of page. Expected: Page position remembered and user returned to that position after pressing Back.
Comment 1•10 years ago
|
||
This bug repro's on: Flame 2.1 Master, Flame 2.0, Flame 1.4 and Buri 2.1 Actual Results: When on a browser page with links, if the user scrolls down the webpage, then taps on a link then taps the back button, the user is returned to the very top of the webpage. **Note** This does not appear to be 100% however. I've tapped the same link twice and been taken to the spot I left off from but the next attempt takes me to the top of the page. Environmental Variables: Device: Flame Master Build ID: 20140715070915 Gaia: 46cd188fdda2397d2b8f3303a184dcd52952e2b2 Gecko: 835e22069c1a Version: 33.0a1 (Master) Firmware Version: v122 ----------------------------------------------- Environmental Variables: Device: Flame 2.0 Build ID: 20140715082614 Gaia: 391258012d09cc1dde9a6f3f9a2078739043d0d6 Gecko: 7025d37f4b06 Version: 32.0a2 (2.0) Firmware Version: v122 ----------------------------------------------- Environmental Variables: Device: Flame 1.4 Build ID: 20140715071209 Gaia: 7e49e66ae1f8f48bb23a4a551a8e393b0ae8a228 Gecko: 37382637c713 Version: 30.0 (1.4) Firmware Version: v122 ----------------------------------------------- Environmental Variables: Device: Buri Master Build ID: 20140715070915 Gaia: 46cd188fdda2397d2b8f3303a184dcd52952e2b2 Gecko: 835e22069c1a Version: 33.0a1 (Master) Firmware Version: v1.2device.cfg
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
Comment 2•10 years ago
|
||
Repro Rate: 8/10
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 3•10 years ago
|
||
Is this specific to b2g or does it happen on the same pages on Android or desktop?
Comment 4•10 years ago
|
||
THis is not a regression and not severe enough to block the release and something we can fix in future release as and it sounds like a feature request.
blocking-b2g: 2.0? → backlog
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 5•10 years ago
|
||
(In reply to Boris Zbarsky [:bz] from comment #3) > Is this specific to b2g or does it happen on the same pages on Android or > desktop? Both Desktop and Fennec remember the location. We should figure out why this fails sometimes on a device that should have plenty of available memory.
Priority: -- → P1
Comment 6•10 years ago
|
||
Although, it appears Fennec is seeing a similar issue. Might be the same.
See Also: → 942736
Comment 7•10 years ago
|
||
Sounds similar to bug 942736, dupe?
Comment 8•10 years ago
|
||
(In reply to Eugen Sawin [:esawin] from comment #7) > Sounds similar to bug 942736, dupe? I hope so! Let's wait until more information surfaces there before duping though.
Assignee | ||
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Comment 9•6 years ago
|
||
Mass closing as we are no longer working on b2g/firefox os.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Comment 10•6 years ago
|
||
Mass closing as we are no longer working on b2g/firefox os.
You need to log in
before you can comment on or make changes to this bug.
Description
•