Tracking: SVG Filter Support #47302
Labels
[Feature] Design Tools
Tools that impact the appearance of blocks both to expand the number of tools and improve the experi
[Type] Tracking Issue
Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
SVG filter support was initially added in the form of Duotone filters in block supports and global styles quite a while ago. The end goal was to enable more creative designs for WordPress websites by leveraging SVG filters. Duotone support was added into core because it isn't too opinionated in design, but the true potential is enabling plugin/theme authors to create their own opinionated filters.
This tracking issue is focusing on issues that are not unique to duotone and would need to be solved for plugin-based SVG filters. Duotone specific issues are tracked in #47304.
Experimental APIs
block.json
API: consider graduating__experimentalSelector
and__experimentalDuotone
from experimental to stable #45194Bugs
Performance Issues
Theme switching
Extensibility (filter plugins)
Block support plugin hooks
This can more-or-less already be achieved. Duotone was initially implemented this way in Automattic/block-experiments using the following filters.
As the plugin has to define which blocks support should be added too, it's rather difficult to support non-core blocks with this approach.
Global styles plugin hooks
There is currently no way to extend global styles definitions using
WP_Theme_JSON
, but in #49103 we experimented with rolling our own global styles through block supports. The last missing piece is merging default, theme, and user origins which is still configured inPRESETS_METADATA
inWP_Theme_JSON
.Safari Bugs
Safari has many more SVG filer related bugs than other major browsers. These are some to be aware of when working on SVG filters in WordPress.
The text was updated successfully, but these errors were encountered: