This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10409 - Adoption agency + SVG bug
Summary: Adoption agency + SVG bug
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P1 critical
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-20 16:51 UTC by Tony Gentilcore
Modified: 2010-10-04 13:59 UTC (History)
6 users (show)

See Also:

Attachments

Description Tony Gentilcore 2010-08-20 16:51:58 UTC 
A fuzzer script generated this strange document:
<a><svg><tr><input></a>

Both webkit and mozilla produce this tree:
| <html>
|   <head>
|   <body>
|     <a>
|       <svg svg>
|     <svg tr>
|       <a>
|   <svg input>
|     <a>

It isn't clear to me what the correct behavior is here, but this can't be right. I haven't spent much time debugging, but since the two implementations agree, that seems to point to a spec bug.
Comment 1 Eric Seidel 2010-08-20 19:20:56 UTC 
Ian wants all implementor bugs marked p1 critical, btw.
Comment 2 Ian 'Hixie' Hickson 2010-08-21 21:49:32 UTC 
WebKit's behaviour here is completely bogus. In fact it's worse that you describe — I find the <input> element in two places in the tree! I can't see how the tree in the bug description could possibly be generated from the spec. It's not what I get in Firefox, validator.nu, or html5lib.

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Does not seem to be a spec bug
Comment 3 Eric Seidel 2010-08-22 00:29:46 UTC 
It appears that Hixie is right, at least for this test case:

http://software.hixie.ch/utilities/js/live-dom-viewer/?%3Ca%3E%3Csvg%3E%3Ctr%3E%3Cinput%3E%3C/a%3E

Does not show the bogus dom for Mozilla, but does in Chromium Dev channel.
Comment 4 Eric Seidel 2010-08-22 17:14:39 UTC 
I believe WebKit's bug here is that we don't check the namespace of <tr> or <input> during the run of the Adoption Agency.  As far as I can tell, the AAA is supposed to run for this code. :)
Comment 5 Eric Seidel 2010-08-22 17:15:16 UTC 
https://bugs.webkit.org/show_bug.cgi?id=44390 tracks fixing WebKit's bug.