[Webkit-unassigned] [Bug 76515] New: Update HTML Parser so that <content> element should be treated transparently.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Jan 17 21:47:19 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=76515
Summary: Update HTML Parser so that <content> element should be
treated transparently.
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: HTML DOM
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: hayato at chromium.org
CC: dglazkov at chromium.org, rolandsteiner at chromium.org,
dominicc at chromium.org, morrita at google.com,
shinyak at chromium.org
Suppose we have <content> element and given the following HTML:
<table>
<content>
<td>hello</td>
</content>
</table>
In the current HTML parser implementation, the result DOM tree would become:
<content>
</content>
<table>
<tbody>
<tr>
<td>hello</td>
</tr>
</tbody>
</table>
Yeah, <content> elements would be put outside of <table> element.
The result should be something like this:
<table>
<content>
<td>hello</td>
</content>
</table>
I am not sure whether we should add <tbody> or <tr> somewhere in this particular case.
At least, current implementation should be modified somehow.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list