Re: [whatwg] Fwd: Range.createContextualFragment in SVG contexts from Anne van Kesteren on 2014-10-28 (public-whatwg-archive@w3.org from October 2014)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 28 Oct 2014 14:56:15 +0100
To: Daniel Trebbien <dtrebbien@gmail.com>
Cc: WHATWG <whatwg@whatwg.org>
Message-ID: <CADnb78hnMd2HrQgqM-=Vc_uKNnhHhM05U_DdftTJF3J-QbyX7g@mail.gmail.com>

On Tue, Oct 28, 2014 at 2:29 PM, Daniel Trebbien <dtrebbien@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
wrong.

-- 
https://annevankesteren.nl/

Received on Tuesday, 28 October 2014 13:56:41 UTC