-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[filters-1] filter region and filter primitive subregion should be defined better for CSS filter functions #23
Comments
See also #2, a feature request to have this same sort of automatic filter region available for |
@dbaron The spec does not state how to compute this area but it does say:
https://drafts.fxtf.org/filters/#filter-region-for-shorthands |
It might be useful to add a note in the "Filter primitive representation" section for But beyond that, I'm fine with keeping this in prose for now. The exact calculation would depend on how far you extend the blur effect (it is theoretically infinite, like a Gaussian curve, but is clamped at a reasonable distance). The definition of |
…ection in shorthand representations. Issue #23.
The filters spec defines new CSS filter functions that do the same thing as some of the SVG filters.
However, I don't see where it defines when (if at all) these filters should be clipped to a rectangle, as is defined much more clearly for SVG filters in the definitions of the filter region and the filter primitive subregion.
This is probably most relevant for the filters where pixels in the input can affect different pixels in the output, i.e., blur() and drop-shadow().
The spec should be clear when (if at all) effects are clipped to a rectangle (e.g., between filter functions, between a CSS filter function and an SVG filter referenced by url(), etc.) and to what rectangle they're clipped.
(I got here, somewhat indirectly, from w3ctag/design-reviews#116 .)
The text was updated successfully, but these errors were encountered: