[Webkit-unassigned] [Bug 76515] Update HTML Parser so that <content> element should be treated transparently.

Wed Jan 18 02:49:52 PST 2012

https://bugs.webkit.org/show_bug.cgi?id=76515

--- Comment #6 from Hayato Ito <hayato at chromium.org>  2012-01-18 02:49:52 PST ---
Hi Adam, thank you for the comment.

I totally agree your concerns. We have to consider all the consequences in addition to the spec change.
Let us continue to pursuit what should be done and use this bug for tracking the issue and updating the status.

(In reply to comment #5)
> > I don't understand how such modification for the parser is tough.
> 
> It's not the modifications themselves that are tough, it's understanding all the consequences.  Have you considered how these documents will be handled by user agents that don't understand these new parsing rules?  What about other insertion modes besides InTable?
> 
> I'm very hesitant to make changes to the parser without those changes first appearing in the HTML living standard.  The cost of having our parser diverge from the standard and from all the other browsers (who now implement the standard) is much higher than in other areas, such as JavaScript APIs.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.