Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-07-31 Thread Ian Hickson
On Thu, 4 Jul 2013, Michael Day wrote: > > > > The problem is that we can't do (2) in _all_ cases, e.g. innerHTML on > > an can't possibly break out of the if it sees one of these > > tags, since that's the "root" of what is being parsed. > > Yes, HTML has already lost the composability of pa

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-07-03 Thread Michael Day
Hi Ian, The problem is that we can't do (2) in _all_ cases, e.g. innerHTML on an can't possibly break out of the if it sees one of these tags, since that's the "root" of what is being parsed. Yes, HTML has already lost the composability of parsing that XML and other languages have, that's l

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-07-03 Thread Ian Hickson
On Thu, 4 Jul 2013, Michael Day wrote: > > > > We don't have any data that says that we need to support this for > > innerHTML. I think it's a win if we can drop the hack from innerHTML. > > Okay, so allowing some HTML elements to break out of foreign content is > a hack added for historical re

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-07-03 Thread Michael Day
Hi Ian, We don't have any data that says that we need to support this for innerHTML. I think it's a win if we can drop the hack from innerHTML. Okay, so allowing some HTML elements to break out of foreign content is a hack added for historical reasons, that will surprise authors and complica

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-07-02 Thread Ian Hickson
On Tue, 2 Jul 2013, Michael Day wrote: > > The new text reads: > > "If the parser was originally created for the HTML fragment parsing algorithm, > then act as described in the "any other start tag" entry below. (fragment > case)" > > This always just adds the HTML element in place inside the fo

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-07-02 Thread Michael Day
Hi Ian, I ended up removing this from the spec for other reasons, so this should be resolved now. Let me know if it's not. (No, I don't know what I had originally intended.) I don't think the new spec is correct. The question is what happens if we are tokenizing some foreign content, and we

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-07-01 Thread Ian Hickson
On Thu, 18 Apr 2013, Michael Day wrote: > > Another issue regarding recent changes to 12.2.5.5 "The rules for > parsing tokens in foreign content". > > When a HTML start tag is seen (specifically "b", "big", "blockquote", > "body", "br", "center", "code", ...) the following procedure is given t

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-06-23 Thread Michael Day
Hi Adam, Since the stack of open elements always has at the top of the stack, the "element in scope" algorithm will always find it, and as a result, the first part of the condition will always fail. Even in the fragment case? (Note the parenthetical remark in the spec about this text applyin

Re: [whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-06-22 Thread Adam Barth
On Thu, Apr 18, 2013 at 12:27 AM, Michael Day wrote: > Another issue regarding recent changes to 12.2.5.5 "The rules for parsing > tokens in foreign content". > > When a HTML start tag is seen (specifically "b", "big", "blockquote", > "body", "br", "center", "code", ...) the following procedure is

[whatwg] Another issue in 12.2.5.5 parsing tokens in foreign content

2013-04-18 Thread Michael Day
Hi, Another issue regarding recent changes to 12.2.5.5 "The rules for parsing tokens in foreign content". When a HTML start tag is seen (specifically "b", "big", "blockquote", "body", "br", "center", "code", ...) the following procedure is given to recover from the parse error: """ If the