Re: //head/object

> When there's a 3 vs. 1 situation with 3 on the side of parser simplicity, I think the spec should follow the 3.
I can't see how it makes those browsers' parsers simpler. Either there's some generic mechanism (implementing an SGML feature) that closes the parent element (head) implicitly, in which case it's simply a matter of whether object is included in the list of tags triggering it, or object is a specific exception to the rule of following the tree structure of the syntax, handled by dedicated code, thus _adding_ complexity.

The general impression I get from this and similar discussions is that corner cases are preferred by some browser vendors to be specified as _inconsistently_ as possible with the rest of Internet technologies (including current versions of the multitude of stuff now being shoved into HTML5).

Best regards,

Krzysztof Maczyński

Received on Tuesday, 4 May 2010 14:21:06 UTC