Contact emails...@chromium.org

ExplainerNone

Specificationhttps://drafts.fxtf.org/css-masking/#the-clip-path

Summary

Clip-path supports <geometry-box> values to control the clip's reference
box, making clip-path easier to use. These box values can be used alongside
basic shapes (for example, clip-path: circle(50%) margin-box), or they can
be used alone to clip to the specified box (for example, clip-path:
content-box).

Blink componentBlink>Paint
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPaint>

Search tagsclip-path <https://chromestatus.com/features#tags:clip-path>,
clipPath <https://chromestatus.com/features#tags:clipPath>, geometry-box
<https://chromestatus.com/features#tags:geometry-box>, geometryBox
<https://chromestatus.com/features#tags:geometryBox>

TAG reviewNone

TAG review statusNot applicable

Risks
Interoperability and Compatibility

Low, as this has already shipped in both Firefox and Safari.

*Gecko*: Shipped/Shipping

*WebKit*: Shipped/Shipping

*Web developers*: Positive (
https://github.com/web-platform-tests/interop/issues/148)

*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

This is debuggable with existing basic CSS tooling.

Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?Yes

Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
?Yes

Flag name on chrome://flagsNone

Finch feature nameClipPathGeometryBox

Requires code in //chrome?False

Tracking bughttps://crbug.com/694218

MeasurementOverall clip-path usage is tracked with
https://chromestatus.com/metrics/css/timeline/popularity/355.

Sample linkshttps://pr.gg/clip-path-geometry-box-examples.html

Estimated milestones
Shipping on desktop 118
Shipping on Android 118
Shipping on WebView 118

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/5068167415595008

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 on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJgFLLsaeiJpz75KQKH-hHoUD%2Bz36mJ4RSKQ9RMWREWSiT9U2A%40mail.gmail.com.

Reply via email to