CSS mask, and related properties such as mask-image, mask-mode, etc, are used to hide an element (partially or fully) by masking or clipping the image at specific points. This feature unprefixes the -webkit-mask* properties and brings them up to spec. This includes mask-image, mask-mode, mask-repeat, mask-position, mask-clip, mask-origin, mask-size, and mask-composite, as well as the "mask" shorthand. Local mask-image references are supported, serialization now matches the spec, and accepted values now match the spec (for example, "add" instead of "source-over" for mask-composite).
There is some compatibility risk in adding an unprefixed feature while still supporting the prefixed version. This is minimized as we are following the same pattern Webkit has already shipped. In addition, Firefox supports several of the legacy -webkit- prefixed properties too.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Basic debugging support with existing CSS support in devtools.
Shipping on desktop | 120 |
DevTrial on desktop | 120 |
Shipping on Android | 120 |
DevTrial on Android | 120 |
Shipping on WebView | 120 |
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).
NoneOn 10/25/23 10:00 AM, Philip Rogers wrote:
Contact emails
p...@chromium.org, tca...@chromium.org, yo...@chromium.org, f...@opera.com
Explainer
None
Specification
https://drafts.fxtf.org/css-masking/#positioned-masks
Design docs
https://developer.mozilla.org/en-US/docs/Web/CSS/mask
Summary
CSS mask, and related properties such as mask-image, mask-mode, etc, are used to hide an element (partially or fully) by masking or clipping the image at specific points. This feature unprefixes the -webkit-mask* properties and brings them up to spec. This includes mask-image, mask-mode, mask-repeat, mask-position, mask-clip, mask-origin, mask-size, and mask-composite, as well as the "mask" shorthand. Local mask-image references are supported, serialization now matches the spec, and accepted values now match the spec (for example, "add" instead of "source-over" for mask-composite).
Blink component
Blink>CSS
TAG review
None
TAG review status
Not applicable
Risks
Interoperability and Compatibility
There is some compatibility risk in adding an unprefixed feature while still supporting the prefixed version. This is minimized as we are following the same pattern Webkit has already shipped. In addition, Firefox supports several of the legacy -webkit- prefixed properties too.
--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJgFLLsO8COSdLuHsEaM2TQWzAf6%2B5wJLt0PcR3QEoyyOb4Rhw%40mail.gmail.com.
On 10/25/23 10:00 AM, Philip Rogers wrote:
Contact emails p...@chromium.org, tca...@chromium.org, yo...@chromium.org, f...@opera.com
Explainer None
Specification https://drafts.fxtf.org/css-masking/#positioned-masks
Design docs https://developer.mozilla.org/en-US/docs/Web/CSS/mask
SummaryCSS mask, and related properties such as mask-image, mask-mode, etc, are used to hide an element (partially or fully) by masking or clipping the image at specific points. This feature unprefixes the -webkit-mask* properties and brings them up to spec. This includes mask-image, mask-mode, mask-repeat, mask-position, mask-clip, mask-origin, mask-size, and mask-composite, as well as the "mask" shorthand. Local mask-image references are supported, serialization now matches the spec, and accepted values now match the spec (for example, "add" instead of "source-over" for mask-composite).
Blink component Blink>CSS
TAG review None
TAG review status Not applicable
Risks
Interoperability and CompatibilityThere is some compatibility risk in adding an unprefixed feature while still supporting the prefixed version. This is minimized as we are following the same pattern Webkit has already shipped. In addition, Firefox supports several of the legacy -webkit- prefixed properties too.
Is there anywhere that documents the differences, beyond what is written in the summary? It would be nice if we can capture that in the Compat standard, where they are no longer simple aliases.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3546ce55-11a4-4017-ae43-69d57a5d20e5n%40chromium.org.
LGTM2.
(I filed https://github.com/whatwg/compat/issues/252 - thanks for
the doc!)
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68b9d7ec-650e-40f3-98cd-679a9ea09f8a%40chromium.org.