Intent to implement and ship: Support offset-path: shape()
Noam Rosenthal
Contact emails
nrose...@chromium.orgExplainer
NoneSpecification
https://drafts.csswg.org/css-shapes-2/#shape-functionSummary
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 component
Blink>CSSTAG review
NoneTAG review status
Not applicableRisks
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)?
NoIs this feature fully tested by web-platform-tests?
NoFlag name on about://flags
NoneFinch feature name
NoneNon-finch justification
NoneRollout plan
Will ship enabled for all usersRequires code in //chrome?
FalseTracking bug
https://issues.chromium.org/issues/389713717Estimated 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).
NoneLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5165902775189504?gate=6308065911242752Noam Rosenthal
Noam Rosenthal
Domenic Denicola
Contact emailsnrose...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/css-shapes-2/#shape-function
SummaryThe 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
TAG reviewNone
TAG review statusNot applicable
Risks
Interoperability and CompatibilityNone
Gecko: No signal
WebKit: Shipped/Shipping
Web developers: No signals
Other signals:
WebView application risksDoes this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
DebuggabilityNone
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?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 milestonesShipping on desktop138Shipping on Android138Shipping on WebView138
Anticipated spec changesOpen 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 Statushttps://chromestatus.com/feature/5165902775189504?gate=6308065911242752
Noam Rosenthal
On Wednesday, April 9, 2025 at 5:17:32 PM UTC+9 Noam Rosenthal wrote:Contact emailsnrose...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/css-shapes-2/#shape-function
SummaryThe 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
TAG reviewNone
TAG review statusNot applicable
Risks
Interoperability and CompatibilityNone
Gecko: No signalCan you file for one? Or maybe this is small enough not to require one, but is there a recorded CSSWG resolution with Gecko participation you could link to?
WebKit: Shipped/Shipping
Web developers: No signals
Other signals:
WebView application risksDoes this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
DebuggabilityNone
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?No
Flag name on about://flagsNone
Finch feature nameNone
Non-finch justificationNonePlease provide one of these two, preferably the Finch feature name.
Rollout planWill ship enabled for all users
Requires code in //chrome?False
Tracking bughttps://issues.chromium.org/issues/389713717
Estimated milestonesShipping on desktop138Shipping on Android138Shipping on WebView138138 has already branched, so just checking that you intend to backport? Or if not, it'd be good to update this to 139.
Domenic Denicola
Daniel Clark
For the record, the TAG did review this (Resolution: satisfied): https://github.com/w3ctag/design-reviews/issues/1033. LGTM2.
-- Dan
--
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+...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra8dU7_5rBnTSvdfN2Ku%3DtA4F%2BLwxVXWW%3Dkim1tcJRgXKA%40mail.gmail.com.
Alex Russell
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
