18291 2012-07-18 17:58:56 +0000 It's unclear here and elsewhere what it means to "cancel the navigation", and what effects it will have e.g. on the parser (presumably it will be like getting EOF?). Could this be clarified, perhaps by rewriting in terms of the abort algorithm? 2012-12-07 10:25:07 +0000 1 1 1 Unclassified HTML.next default unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#dom-window-stop P3 normal --- 1 contributor silviapfeiffer1 hsivonen ian mike public-html-admin public-html-wg-issue-tracking robin silviapfeiffer1 public-html-bugzilla oldest_to_newest 71047 0 contributor 2012-07-18 17:58:56 +0000 This was was cloned from bug 16801 as part of operation convergence. Originally filed: 2012-04-19 16:04:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-04-19 16:04:59 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#dom-window-stop Complete: http://www.whatwg.org/c#dom-window-stop Comment: It's unclear here and elsewhere what it means to "cancel the navigation", and what effects it will have e.g. on the parser (presumably it will be like getting EOF?). Could this be clarified, perhaps by rewriting in terms of the abort algorithm? Posted from: 2001:4c28:a030:30:219:99ff:fe0e:5501 User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.10.282 Version/12.00 ================================================================================ #1 Henri Sivonen 2012-04-23 06:42:30 +0000 -------------------------------------------------------------------------------- window.stop() in WebKit and Gecko and document.execCommand('Stop') in Trident abort the parser (the latter not for script-created parsers): http://hsivonen.iki.fi/test/moz/readystate/window-stop.html http://hsivonen.iki.fi/test/moz/readystate/document-open-window-stop.html http://hsivonen.iki.fi/test/moz/readystate/execcommand.html http://hsivonen.iki.fi/test/moz/readystate/document-open-execcommand.html ================================================================================ #2 Ian 'Hixie' Hickson 2012-07-10 18:56:22 +0000 -------------------------------------------------------------------------------- This may be clearer now that in the WHATWG copy it says both to cancel the navigation (which I think is already clearly defined to just mean aborting that "navigate" algorithm) _and_ abort the document. ================================================================================ 73857 1 robin 2012-09-14 09:46:25 +0000 *** Bug 18121 has been marked as a duplicate of this bug. *** 73859 2 robin 2012-09-14 09:48:12 +0000 *** Bug 18119 has been marked as a duplicate of this bug. *** 79633 3 silviapfeiffer1 2012-12-07 10:25:07 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/185e037dd424602f570a427c169d51cb59661390 Rationale: Moving this to HTML.next (HTML5.1) because the patch from WHATWG is more involved; it is now applied to the master branch