- From: Simon Fraser via GitHub <noreply@w3.org>
- Date: Fri, 06 Jun 2025 00:09:13 +0000
- To: public-css-archive@w3.org
smfr has just created a new issue for https://github.com/w3c/csswg-drafts: == [filter-effects] What's the order of applying filters and `overflow`? == https://drafts.fxtf.org/filter-effects/#FilterProperty says: > The compositing model follows the [SVG compositing model](https://www.w3.org/TR/SVG11/render.html#Introduction) [[SVG11]](https://drafts.fxtf.org/filter-effects/#biblio-svg11): first any filter effect is applied, then any clipping, masking and opacity. As per SVG, the application of [filter](https://drafts.fxtf.org/filter-effects/#propdef-filter) has no effect on hit-testing. which implies that `overflow` (a type of clipping) is applied after the filter. This suggests that `overflow:clip` would clip out the part of a drop-shadow filter that extends outside the box. However, Chrome and Firefox don't do this, but WebKit does. Test: https://codepen.io/smfr/pen/XJbRaeb Or does the `clipping` above only apply to `clip-path`, which is more akin to SVG-style clipping? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12291 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 June 2025 00:09:14 UTC