[whatwg] several messages
ian at hixie.ch
Thu Jun 21 22:49:36 PDT 2007
On Thu, 21 Jun 2007, Anne van Kesteren wrote:
> Currently if you encounter </body> or </html> inside a <noscript>
> element in the scripting disabled case you will get incorrect results as
> the current node is not the <head> element but the <noscript> element.
Hm, indeed, you'd get an infinite loop. Fixed.
On Thu, 21 Jun 2007, Simon Pieters wrote:
> On Thu, 21 Jun 2007 10:59:18 +0200, Ian Hickson <ian at hixie.ch> wrote:
> > > If we want to allow NOSCRIPT in HEAD, then it seems to me that the most
> > > logical way to parse non-HEAD content inside it (which would be a parse
> > > error) is to pop the NOSCRIPT element and then reprocess as if it was
> > > found in HEAD directly.
> > That's what I did (though I did it for some head content too; let me
> > know if you think there are use cases for the other cases).
> I can think of meta refresh as being potentially useful (e.g., if you
> want a news page to update itself, but with XHR if scripting is enabled,
> or something).
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg