Re: [svgwg] stacking context / rendering order requirements are mostly not Web compatible (#463)

In CSS setting the transform property triggers the creation of a new stacking context - this is explicitly omitted from https://svgwg.org/svg2-draft/render.html#EstablishingStackingContex.

CSS Transforms Module Level 1 says:
For elements whose layout is governed by the CSS box model, any value other than none for the transform property results in the creation of a stacking context. Implementations must paint the layer it creates, within its parent stacking context, at the same stacking order that would be used if it were a positioned element with z-index: 0. If an element with a transform is positioned, the z-index property applies as described in [CSS2], except that auto is treated as 0 since a new stacking context is always created.

But there is no explicit statement about SVG. It is inconsistent if the CSS property "transform" applied on HTML content triggers a new stacking context, but not when applied to SVG elements.

I can imagine good reasons for both scenarios, but it is inconsistent from spec point of view at present. Please enlighten me what I might be mising.



-- 
GitHub Notification of comment by nikolaszimmermann
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/463#issuecomment-550306254 using your GitHub account

Received on Wednesday, 6 November 2019 13:22:25 UTC