10409 2010-08-20 16:51:58 +0000 Adoption agency + SVG bug 2010-10-04 13:59:59 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED WONTFIX P1 critical --- 1 tonyg ian eric ian mike public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 37669 0 tonyg 2010-08-20 16:51:58 +0000 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. 37674 1 eric 2010-08-20 19:20:56 +0000 Ian wants all implementor bugs marked p1 critical, btw. 37681 2 ian 2010-08-21 21:49:32 +0000 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 37684 3 eric 2010-08-22 00:29:46 +0000 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. 37700 4 eric 2010-08-22 17:14:39 +0000 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. :) 37701 5 eric 2010-08-22 17:15:16 +0000 https://bugs.webkit.org/show_bug.cgi?id=44390 tracks fixing WebKit's bug.