- From: James Graham <jgraham@opera.com>
- Date: Fri, 15 Jun 2012 12:07:11 +0200
- To: whatwg@lists.whatwg.org
On 06/14/2012 04:38 PM, James Graham wrote: > On 06/13/2012 11:18 PM, Ian Hickson wrote: >> On Fri, 20 Apr 2012, Henri Sivonen wrote: >>>> >>>> * Should window.stop() really not abort the parser like the spec >>>> seems to suggest? >>> >>> Looks like Opera is alone with the non-aborting behavior. The spec is >>> wrong. >> >> Can you elaborate on this? How can you tell? > > I presume the TC is something like > > <!doctype html> > Before stop > <script> > window.stop() > </script> > After stop > > > Only Opera displays "after stop" here. We are planning to change this > behaviour, so that window.stop is much more like the "abort the > document" (I haven't yet closely studied how this interacts with the > readystate and other things that Henri has been looking at). FWIW I think the conceptually simplest solution here is for aborting the document to go through "The End", so that defer scripts are run, DOMContentLoaded and load events fire, and the readyState changes in the normal way. This isn't quite like the behaviour of Gecko or WebKit today, but is spec-wise easy to understand, and hopefully no one is relying too much on specific behaviour of window.stop().
Received on Friday, 15 June 2012 10:07:59 UTC