On Tue, Oct 28, 2014 at 2:29 PM, Daniel Trebbien <dtrebb...@gmail.com> wrote:
> The issue that I am referring to is the behavior of
> Range.createContextualFragment() when the context node is not an SVG <svg>
> element, but some other SVG element such as an SVG <defs> or <g> element.

If you change the range's start node to e.g. the <defs> element,
you'll find Firefox reports two child nodes, just like Chrome.

I think given https://www.w3.org/Bugs/Public/show_bug.cgi?id=17924 and
https://html5.org/r/7768 we were probably reading the specification


Reply via email to