- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sun, 24 Dec 2017 04:23:58 +0000
- To: public-fxtf-archive@w3.org
@dirkschulze Good question. No, I didn't check. Now I have. Results aren't pretty. Test case: https://codepen.io/AmeliaBR/pen/5670978ec8f6904558d57aa6f66ca2de/ Tests run in EdgeHTML 16, Chrome 63, Firefox 58, and Safari 11. Chrome, Safari, and Edge do not support `clip` on any elements with SVG layout. (They support it on absolutely positioned top-level `<svg>` elements, based on the CSS box layout requirements.) Firefox supports `clip` for SVG, but inconsistently: - a `clip` is applied on `<svg>`, `<image>`, and `<marker>`, but not on `<symbol>` or `<pattern>` - I suspect that `<symbol>` (which Firefox formerly implemented as a nested `<svg>` in the shadow DOM) would probably have been clipped prior to FF 56, but that was broken by the recent fixes to symbol style matching (it is now a separate element type, which must not have `clip` specifically turned on). - To confuse things even more, a `clip` on a nested `<svg>` is applied in the parent coordinate system, but on a `<marker>` it gets applied in the marker's own `viewBox` coordinates. ______________________________________ At this point, I'd be tempted to just say that `clip` doesn't apply to elements that don't have CSS layout boxes. After all, SVG has had `clip-path` for as long as it has had `clip`, so there isn't much legacy use case. But I don't know if there are any uses of it in non-browser SVG contexts. Maybe check with your own colleagues at Adobe and with @Tavmjong, for starters. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/197#issuecomment-353764504 using your GitHub account
Received on Sunday, 24 December 2017 04:24:02 UTC