22322 2013-06-10 22:47:12 +0000 Where possible, replace parts of the parser that say "act as is a ... tag had been seen" with explicit requirements to act appropriately (e.g. pop the stack, add elements, etc) 2013-07-03 14:19:52 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#tree-construction P1 blocker Unsorted 17930 21308 1 contributor ian adamk adrianba annevk hsivonen ian james mike rafaelw tross w3c zcorpan contributor oldest_to_newest 89034 0 contributor 2013-06-10 22:47:12 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#tree-construction Complete: http://www.whatwg.org/c#tree-construction Referrer: Comment: Where possible, replace parts of the parser that say "act as is a ... tag had been seen" with explicit requirements to act appropriately (e.g. pop the stack, add elements, etc) Posted from: 2620:0:1000:147c:e6ce:8fff:fe07:8094 by ian@hixie.ch User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1521.3 Safari/537.36 89035 1 ian 2013-06-10 22:50:11 +0000 I don't know how plausible this is, but it would make the parser easier to understand, which would then make solving the problems with namespaces more tractable. Any opinions? Before doing this throughout I'd try to do it in a few places to make sure it was itself tractable and to make sure we were all on the same page. 89145 2 annevk 2013-06-12 06:14:12 +0000 Sounds okay to me. 89150 3 hsivonen 2013-06-12 07:29:45 +0000 Seems superficially OK. The V.nu parser tends to inline "as if" stuff anyway. 90014 4 ian 2013-06-28 23:05:39 +0000 The main idea here would be to remove the parser's assumption in the html section that we're not in a foreign section (or that if we are, that the fake tokens it's generating are going to match html nodes, not foreign ones). Ideally, this will then fix bug 21308, or at least make it much more obvious what needs fixing to address the problems there. 90078 5 ian 2013-07-01 19:24:39 +0000 Note to self: I'm not inlining the AAA into the <a> start tag step. 90079 6 ian 2013-07-01 19:25:12 +0000 Same for <nobr>. 90083 7 ian 2013-07-01 20:48:38 +0000 And not inlining </script> in foreign content either. But that one seems safe. 90085 8 contributor 2013-07-01 21:19:56 +0000 Checked in as WHATWG revision r8001. Check-in comment: Change the HTML parser from using 'act as if' tokens to inlining the behaviour. The only normative changes should be the number of 'parse errors' detected in certain edge cases. Three occurrences of 'act as if' remain. This should make it a lot easier to fix the spec's namespace issues. http://html5.org/tools/web-apps-tracker?from=8000&to=8001 90087 9 contributor 2013-07-01 21:49:28 +0000 Checked in as WHATWG revision r8002. Check-in comment: Remove the remaining 'act as if' cases. This _should_ be an entirely editorial fix, but reviews are definitely encouraged... http://html5.org/tools/web-apps-tracker?from=8001&to=8002 90222 10 ian 2013-07-03 14:19:52 +0000 Let me know if I missed anything!