This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 17041 as part of operation convergence. Originally filed: 2012-05-12 04:00:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-05-12 04:00:46 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html Multipage: http://www.whatwg.org/C#the-location-interface Complete: http://www.whatwg.org/c#the-location-interface Comment: Setting location before the page is done loading shouldn't always be a replace load Posted from: 71.184.125.56 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1 ================================================================================ #1 Boris Zbarsky 2012-05-12 04:02:01 +0000 -------------------------------------------------------------------------------- See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-July/027372.html for a survey of browser behavior and https://bugzilla.mozilla.org/show_bug.cgi?id=754029#c5 for the reason why the current spec behavior is not really all that great: it makes user interactions race with page loading in undesirable ways. ================================================================================
Already fixed in nightly/ED. See https://www.w3.org/Bugs/Public/show_bug.cgi?id=17041 and https://html5.org/r/7882 and https://github.com/whatwg/html-mirror/commit/06849ebef56d9c44249bfa8876629e6d91e6a37e
Re-opening and re-prioritizing so we can (re)confirm the fix. And again noting this seems to already be fixed in the W3C nightly/ED. See https://www.w3.org/Bugs/Public/show_bug.cgi?id=17041 and https://html5.org/r/7882 and https://github.com/whatwg/html-mirror/commit/06849ebef56d9c44249bfa8876629e6d91e6a37e
Noting this simply editorial.
Noting that while editorial there's also a possible interop issue here.
HTML5.1 Bugzilla Bug Triage: Fixed and merged The fix as applied below is now integrated into HTML 5.1 > Checked in as WHATWG revision r7882. > Check-in comment: Keep pages in history even if they were still loaded when the user navigated away (but still not if a script did it on its own). http://html5.org/tools/web-apps-tracker?from=7881&to=7882 If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!