Re: [fxtf-drafts] [css-masking-1] Let SVGClipPathElement and SVGMaskElement inherit from SVGGraphicsElement

The Working Group just discussed `Let SVGClipPathElement and SVGMaskElement inherit from SVGGraphicsElement`.

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: Let SVGClipPathElement and SVGMaskElement inherit from SVGGraphicsElement<br>
&lt;krit> GitHub: https://github.com/w3c/fxtf-drafts/issues/28<br>
&lt;AmeliaBR> Github: https://github.com/w3c/fxtf-drafts/issues/28<br>
&lt;AmeliaBR> Dirk: Sebastien proposed that clipPath and mask should inherit from SVGGraphicsElement, since they are grouping elements<br>
&lt;AmeliaBR> https://svgwg.org/svg2-draft/types.html#InterfaceSVGGraphicsElement<br>
&lt;AmeliaBR> Dirk: This adds interfaces like getBBox.<br>
&lt;AmeliaBR> ... The question is, how does that interact with things like objectBoundingBox units and so on?<br>
&lt;AmeliaBR> ... I definitely don't want to add it to level one, because no implementations yet, I'm not sure whether it's a good idea even in a future level.<br>
&lt;AmeliaBR> Bogdan: Again, this is something where it would add a lot of implementation complexity. It's also not clear what the real use case is, beyond it would be nice to have.<br>
&lt;AmeliaBR> Amelia: Other methods on the interface, like getScreenCTM, wouldn't make sense on never-rendered elements. So there would need to be a significant reorganization of what these interfaces mean.<br>
&lt;AmeliaBR> Dirk: I propose resolving not to add to level 1, with no comment about defferring.<br>
&lt;AmeliaBR> s/defferring/deferring/<br>
&lt;BogdanBrinza> resolution: Do not add SVGClipPathElement and SVGMaskElement inheritance from SVGGraphicsElement to level 1<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/28#issuecomment-368631951 using your GitHub account