On Mon, May 20, 2013 at 2:33 PM, Dirk Schulze <dschulze@adobe.com> wrote:
>
> On May 20, 2013, at 2:08 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>
> > On Mon, May 20, 2013 at 1:55 PM, Dirk Schulze <dschulze@adobe.com>
> wrote:
> >> On May 20, 2013, at 11:16 AM, Rik Cabanier <cabanier@gmail.com> wrote:
> >>> All,
> >>>
> >>> I was editing the chapter on isolation [1] and wondered if inline svg
> should happen in an isolated group. (So the <svg> tag would establish a new
> group/stacking context)
> >>> It seems that it would be very hard to implement if this was not the
> case.
> >>>
> >>> Is everyone that inline SVG is always isolated?
> >>>
> >>> We also need to discuss what other constructs in SVG create isolation.
> The current filter spec assumes that nothing does, but that doesn't
> correspond with reality.
> >>
> >> The first question is how inline SVG cooperates with HTML in general.
> We did not specify that anywhere to my knowledge. In Blink and WebKit
> inline SVG elements are handled as replacement elements, same as <img>,
> <video> or <canvas>. It would make sense to not treat inline SVG elements
> different from the other elements for these two engines.
> >
> > Agreed, and this means that they're an isolated group for the purpose
> > of compositing.
>
> I am absolutely fine with that. I am just curious what the technical
> problems are.
>
Do you mean technical problems from a spec's standpoint or from the
browser's standpoint?