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

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from Adam Barth <abarth at webkit.org>  2012-01-18 01:19:54 PST ---
> 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.