Open Bug 1057392 Opened 10 years ago Updated 2 years ago

Page anchor is scrolled to wrong position after full page refresh

Categories

(Core :: DOM: Navigation, defect)

defect

Tracking

()

Tracking Status
e10s - ---

People

(Reporter: bkelly, Unassigned)

References

()

Details

(Keywords: parity-chrome, parity-edge, parity-ie)

Go to this page in e10s mode: http://slightlyoff.github.io/ServiceWorker/spec/service_worker/#service-worker-global-scope-script-cache Perform a full refresh (shift-ctrl-r). I am consistently placed at "3.2.6 Event handlers" instead of the correct "4.1.1 scriptCache". Not sure this is the correct product/category...
works for me
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160204004009 The issue is still reproducible for me on the latest Aurora 46.0a2 on Windows 10, Mac OS X 10.10 and Ubuntu 15.04. Reproduced the issue by using the following steps: 1. Navigate to: http://slightlyoff.github.io/ServiceWorker/spec/service_worker/ 2. Scroll down and in the Table of Contents click on "4.1 ServiceWorkerGlobalScope" 3. Refresh by hitting the keys: Ctrl+Shift+R. Expected results: The page is refreshed and I should be placed at "4.1 ServiceWorkerGlobalScope". http://slightlyoff.github.io/ServiceWorker/spec/service_worker/#service-worker-global-scope Actual results: The page is refreshed but I'm placed at "3.4 ServiceWorkerContainer" This is reproducible regardless if e10s is enabled or disabled. Setting the status of this report to REOPENED.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
not e10s specific.
Keywords: qawanted
Summary: [e10s] anchors leave page in wrong position on full refresh → Page anchor is scrolled to wrong position after full page refresh
Status: REOPENED → NEW
Whiteboard: [parity-IE] [parity-Chrome][parity-Edge]
Since originally reporting this bug I've realized that the service worker spec is dynamically changing its style/layout. I believe its this dynamic change which causes the scroll position to be off. I suspect they are using some kind of web components polyfil.
See Also: → 1285800
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Whiteboard: [parity-IE] [parity-Chrome][parity-Edge]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.