Re: [whatwg] Stability of tokenizing/dom algorithms

2008-12-14 Thread Ian Hickson
On Sun, 14 Dec 2008, Edward Z. Yang wrote: > > I was curious to know how stable/complete HTML 5's tokenizing and DOM > algorithms are (specifically section 8). Pretty stable. There are some known issues [1], and more issues will surely be found as implementations grow in usage, but the basic a

Re: [whatwg] Stability of tokenizing/dom algorithms

2008-12-14 Thread Geoffrey Sneddon
On 14 Dec 2008, at 21:55, Edward Z. Yang wrote: Are there any specific differences that pose problems? Not that I know of yet, since I haven't started on an implementation yet. Which brings me back to my original question: how stable is section 8? I would rather not be chasing a moving tar

Re: [whatwg] salvaging work while navigating away from a web app -- onunload="confirm('save before quitting?')

2008-12-14 Thread Andy Lyttle
On Sun, Dec 14, 2008 at 10:30 PM, Martin Atkins wrote: An alternative from Opera: The confirm dialog is whole-browser-modal, but it has a checkbox captioned "Stop executing scripts on this page" which allows you to forcefully kill off a script that's repeatedly displaying dialogs as in the

Re: [whatwg] Stability of tokenizing/dom algorithms

2008-12-14 Thread Edward Z. Yang
Anne van Kesteren wrote: > Could you explain what is not sufficient about the the "Parsing HTML > fragments" section: I must admit, I had not seen that section! That seems to be quite sufficient. My bad. :o) > Are there any specific differences that pose problems? Not that I know of yet, since I

Re: [whatwg] Stability of tokenizing/dom algorithms

2008-12-14 Thread Anne van Kesteren
On Sun, 14 Dec 2008 22:37:40 +0100, Edward Z. Yang wrote: 1. Users input HTML fragments, not actual HTML documents. A parser I would use needs to be able to enter parsing in a specific state, and has to ignore any requests by the user to exit that state (i.e. a tag) Could you explain what

[whatwg] Stability of tokenizing/dom algorithms

2008-12-14 Thread Edward Z. Yang
Hello all, I was curious to know how stable/complete HTML 5's tokenizing and DOM algorithms are (specifically section 8). A cursory glance through the section reveals a few red warning boxes, but these are largely issues of whether or not the specification should follow browser implementations, an

Re: [whatwg] salvaging work while navigating away from a web app -- onunload="confirm('save before quitting?')

2008-12-14 Thread timeless
On Sun, Dec 14, 2008 at 10:30 PM, Martin Atkins wrote: > An alternative from Opera: > > The confirm dialog is whole-browser-modal, but it has a checkbox captioned > "Stop executing scripts on this page" which allows you to forcefully kill > off a script that's repeatedly displaying dialogs as in t

Re: [whatwg] salvaging work while navigating away from a web app -- onunload="confirm('save before quitting?')

2008-12-14 Thread Martin Atkins
timeless wrote: On Fri, Dec 12, 2008 at 10:01 PM, Martin Atkins wrote: I think this makes a good case for not allowing any site to create browser-modal UI. Could browsers handle confirm() and friends in such a way that they only block the contents of the tab, not the whole browser? sure given

Re: [whatwg] salvaging work while navigating away from a web app -- onunload="confirm('save before quitting?')

2008-12-14 Thread timeless
On Fri, Dec 12, 2008 at 10:01 PM, Martin Atkins wrote: > I think this makes a good case for not allowing any site to create > browser-modal UI. Could browsers handle confirm() and friends in such a way > that they only block the contents of the tab, not the whole browser? sure given many years an