(please disregard this correction, offset-path: path() is already supported).
On Wed, Apr 9, 2025 at 1:38 PM Noam Rosenthal <nrosent...@chromium.org> wrote: > I amended the title to include the path() function as well which is > missing from offset-path, as it's the same code change. > > On Wed, Apr 9, 2025 at 9:17 AM Noam Rosenthal <nrosent...@chromium.org> > wrote: > >> Contact emailsnrosent...@chromium.org >> >> ExplainerNone >> >> Specificationhttps://drafts.csswg.org/css-shapes-2/#shape-function >> >> Summary >> >> The shape() function is already supported in clip-path, and allows >> responsive clipping. Enabling it also for offset-path will close a small >> gap where the same kind of shape can be used for that property as well. >> >> >> * (already works in Safari and covered by WPTs) >> >> >> Blink componentBlink>CSS >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> None >> >> >> *Gecko*: No signal >> >> *WebKit*: Shipped/Shipping >> >> *Web developers*: No signals >> >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None >> >> >> Debuggability >> >> None >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?No >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?No >> >> Flag name on about://flagsNone >> >> Finch feature nameNone >> >> Non-finch justificationNone >> >> Rollout planWill ship enabled for all users >> >> Requires code in //chrome?False >> >> Tracking bughttps://issues.chromium.org/issues/389713717 >> >> Estimated milestones >> Shipping on desktop 138 >> Shipping on Android 138 >> Shipping on WebView 138 >> >> Anticipated spec changes >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> None >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5165902775189504?gate=6308065911242752 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYY%3DLqP2Nii-Y%3DFFf0vpAqino7Gf245ZxyWnHi5ZcuA1YQ%40mail.gmail.com.
