On Tue, Nov 11, 2008 at 11:21 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Tue, 11 Nov 2008, Garrett Smith wrote:
Unfortunately, we have little choice in the matter. Scripting and XML
both allow you to unambiguously create highly non-conforming DOMs,
e.g. with title elements as the root
On Wed, 12 Nov 2008, Garrett Smith wrote:
A script that adds an HTML element to a INPUT element should cause an
hierarchy exception to be raised.
No, it shouldn't.
DOM 1 seems to disagree with that.
You are misreading DOM1 (the type of a node means text node vs element
node, not
Ian Hickson wrote:
On Mon, 10 Nov 2008, Tommy Thorsen wrote:
FWIW: In our implementation, I've changed the handling of base and
title in in body to:
Process the token using the rules for the after head insertion
mode.
instead of processing them with the rules for in head.
Ian Hickson wrote:
On Mon, 10 Nov 2008, Tommy Thorsen wrote:
From an implementors point of view, it's good to have clearly defined
boundaries between modules. An implementation would typically have one
module that tokenises and parses html and one module that renders the
resulting dom to the
On Mon, Nov 10, 2008 at 7:59 AM, Ian Hickson [EMAIL PROTECTED] wrote:
On Mon, 10 Nov 2008, Tommy Thorsen wrote:
On Mon, 10 Nov 2008, Tommy Thorsen wrote:
From an implementors point of view, it's good to have clearly defined
boundaries between modules. An implementation would typically have
On Tue, 11 Nov 2008, Garrett Smith wrote:
Unfortunately, we have little choice in the matter. Scripting and XML
both allow you to unambiguously create highly non-conforming DOMs,
e.g. with title elements as the root element and html elements as
children of input elements. The renderer
On Mon, 10 Nov 2008 11:51:34 +0100, Tommy Thorsen [EMAIL PROTECTED]
wrote:
I noticed that, according to the html5 algorithm, when the parser sees a
title start tag when in the in body insertion mode, it's not
supposed to relocate it to the head element. Opera matches this
behaviour, but
Simon Pieters wrote:
The description of the title element in the spec (4.2.2 The title
element) says:
Contexts in which this element may be used:
In a head element containing no other title elements.
I don't care very strongly about whether or not title elements are
allowed
On Mon, 10 Nov 2008 15:31:48 +0100, Tommy Thorsen [EMAIL PROTECTED]
wrote:
Simon Pieters wrote:
The description of the title element in the spec (4.2.2 The title
element) says:
Contexts in which this element may be used:
In a head element containing no other title elements.
I
I noticed that, according to the html5 algorithm, when the parser sees a
title start tag when in the in body insertion mode, it's not
supposed to relocate it to the head element. Opera matches this
behaviour, but Firefox moves any title tag it finds into the head element.
The description of
On Mon, 10 Nov 2008, Tommy Thorsen wrote:
I don't care very strongly about whether or not title elements are
allowed anywhere, but I do think the output of the parsing algorithm
should be valid html according to the rest of the spec. So, in my
opinion, we need to change either the allowed
11 matches
Mail list logo
