W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2014

Re: [whatwg] Fwd: Range.createContextualFragment in SVG contexts

From: Daniel Trebbien <dtrebbien@gmail.com>
Date: Tue, 28 Oct 2014 09:29:36 -0400
Message-ID: <CABrgu5RQ0hEB8s6-uKVm3AGVR9tRXYb_QT3izmu-y6zuoqSAwQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WHATWG <whatwg@whatwg.org>
On Tue, Oct 28, 2014 at 8:45 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Oct 28, 2014 at 1:35 PM, Daniel Trebbien <dtrebbien@gmail.com>
> wrote:
> > Issues related to Range.createContextualFragment() in SVG contexts are
> > starting to come up in bug reports:
> > - https://bugzilla.mozilla.org/show_bug.cgi?id=1087715
> > - https://code.google.com/p/chromium/issues/detail?id=426400
> >
> > Should Cameron's idea for changing the HTML fragment parsing algorithm be
> > implemented?
>
> Now Firefox' fragment parsing is fixed, it seems it behaves the same
> as Chrome. Not sure what's going on.
>


I linked to the Firefox bug report mainly for context.  Firefox' behavior
seems correct now, and I can confirm that the modified jsFiddle
<http://jsfiddle.net/hfvz7srp/1/> is working correctly in Firefox Nightly
36.0a1 (2014-10-28).

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.
Received on Tuesday, 28 October 2014 13:30:04 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:24 UTC