<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add API to allow disabling scroll restoration on history navigation"
href="https://bugs.webkit.org/show_bug.cgi?id=147782">147782</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Add API to allow disabling scroll restoration on history navigation
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>528+ (Nightly build)
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>History
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>majidvp@chromium.org
</td>
</tr></table>
<p>
<div>
<pre>Currently there is no reliable and cross-browser solution for developers to opt out the automatic scroll restoration behavior or control any of its aspects.
The automatic restoration works well for document style web sites but it is often not appropriate for single-page web applications where they are
re-constructing the page content onpopstate every time and often asynchronously or need to control the visual transition between states.
Here is more the problem background and existing workarounds: <a href="http://majido.github.io/scroll-restoration-proposal/">http://majido.github.io/scroll-restoration-proposal/</a>
We in blink team have proposed a solution to this issue on WHATWG and there is some consensus (with spec editors and Mozilla experts) around a simple API based on a new attribute added to the history object.
I would like to know if Webkit has any feedback on this solution and API and help make the consensus more inclusive if possible.
Unofficial spec: <a href="http://majido.github.io/scroll-restoration-proposal/history-based-api.html">http://majido.github.io/scroll-restoration-proposal/history-based-api.html</a>
Web platform tests: <a href="http://majido.github.io/scroll-restoration-proposal/tests/">http://majido.github.io/scroll-restoration-proposal/tests/</a>
WhatWG discussion thread: <a href="https://lists.w3.org/Archives/Public/public-whatwg-archive/2015Mar/0070.html">https://lists.w3.org/Archives/Public/public-whatwg-archive/2015Mar/0070.html</a>
WICG discourse: <a href="http://discourse.wicg.io/t/disabling-automatic-scroll-restoration-on-navigation/1012/2">http://discourse.wicg.io/t/disabling-automatic-scroll-restoration-on-navigation/1012/2</a>
Also you can find a summary of alternative APIs and solutions that were considered before reaching the current design here: <a href="http://discourse.wicg.io/t/disabling-automatic-scroll-restoration-on-navigation/1012/4?u=majidvp">http://discourse.wicg.io/t/disabling-automatic-scroll-restoration-on-navigation/1012/4?u=majidvp</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>