[Bug 9659] Initial U+0000 should not set frameset-ok to "not ok"

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9659

--- Comment #20 from Henri Sivonen <hsivonen@iki.fi> 2010-09-30 14:08:55 UTC ---
(In reply to comment #19)
> Checked in as WHATWG revision r5563.
> Check-in comment: Revamp how the foreign lands are defined to make it easier to
> add the U+0000 handling. This checkin should have no normative effect. If there
> are any normative changes in this patch, that's a bug, pleasel let me know
> ASAP.
> http://html5.org/tools/web-apps-tracker?from=5562&to=5563

If you are refactoring foreign lands, why aren't you refactoring them so that
start tag processing first checks if the current node is a foreign node and
then falls through to per-insertion mode behavior if the current node wasn't a
foreign node or when the spec currently forwards to the secondary mode?

So far, putting the foreign-is-a-mode optimization in the spec has caused a
whole bunch of bad behavior in edge cases and the only justification I've seen
so far is the avoidance of a branch per start tag.

I think branch per tag avoidance optimizations should belong in
implementations--not the spec. Particularly when this particular optimization
has caused bogus behavior in edge cases.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 30 September 2010 14:08:58 UTC