On Thu, 5 Jul 2012, Boris Zbarsky wrote: > > It's a violation of HTML5, but so, technically, is the entire Firefox > event loop. HTML5 specifies a very specific set of event queues, and > implementing pretty much anything other than exactly that is likely to > lead to page-visible spec bugs. Of course the slow script dialog itself > is technically a spec violation..... > > In any case, I believe we are in the process of moving to a more > HTML5-like setup here (with multiple per-page event queues, etc), which > should more or less fix most of these issues: we'd just disable all of a > page's event queues when the slow script dialog comes up. > > Note that I say "most". There are some fundamental problems here. Say > the user decides to close the tab or window when they get the slow > script prompt (something that I think is desirable to allow the user to > do, personally). Should this close the tab/window without firing unload > events (a spec violation) or should it fire them while other script from > the page is on the stack and at some random point in its execution (hey, > another spec violation)?
Good points. I have made a note of your e-mail and will in due course ensure that the slow-scripts dialog and harsh termination of a tab are not violations of the HTML spec. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
