711821 - Range.createContextualFragment sets wrong namespace when context is an SVG node

Status: UNCONFIRMED

(Core :: DOM: Core & HTML, defect, P5)

Description

[Victor Costan]

Attachment: Test case

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.12 Safari/535.11

Steps to reproduce:

I used the createContextualFragment DOM Range API, with the context element set to a SVG element. I attached a reduced test case.

Spec at http://html5.org/specs/dom-parsing.html#dom-range-createcontextualfragment



Actual results:

The nodes in the resulting DocumentFragment have their namespaces set to the HTML namespace, not to the SVG namespace.


Expected results:

The nodes in the resulting DocumentFragment should have their namespaces set to the SVG namespace, so I can add them to the SVG element :)

In the attached test case, the black <circle> coming from the SVG fragment should overlap the red <circle> in the initial SVG.

Comment 1

[Victor Costan]

Chrome bug at http://crbug.com/107982

Comment 2

[Victor Costan]

This would be useful for visualizations and games. A real use-case is that I'd like to pull data for a unit model, set it as a <symbol>, and then <use> it to render multiple units with the same model.

Thank you for looking into this!

Comment 3

[Robert Longson [:longsonr]]

That's what the specification says. Have you emailed the whatwg and suggested it be changed?

Comment 4

[Victor Costan]

Thank you for your answer, Robert!

I'd definitely like to email the WHATWG if this is spec behavior, because I don't think it's the right thing to do. Can you please help me where did my train of thought fail?

1. The fragment parser will be invoked with <svg> as the context element.
http://html5.org/specs/dom-parsing.html#dom-range-createcontextualfragment

2. The XML parsing algorithm will be selected.
http://html5.org/specs/dom-parsing.html#concept-parse-fragment

3. The default namespace will be the SVG namespace.
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-xhtml-syntax.html#xml-fragment-parsing-algorithm

Thank you so much!

Comment 5

[Victor Costan]

FWIW, this works now in Chrome.
http://src.chromium.org/viewvc/blink?view=revision&revision=176569

Comment 6

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.