I've noticed that CL also implements the two-value syntax for `mask-position-x/y`. Could you update this information in Chromestatus? This would be helpful for web compatibility. https://chromium-review.googlesource.com/c/chromium/src/+/6811401/10/third_party/blink/web_tests/wpt_internal/css/css-masking/parsing/webkit-mask-position-x-valid.html 在2025年9月22日星期一 UTC+8 16:34:29<Chromestatus> 写道：
> *Contact emails* > [email protected] > > *Explainer* > None > > *Specification* > https://drafts.csswg.org/css-backgrounds-4/#background-position-longhands > > *Summary* > Defines the background image's position relative to one of its edges. This > syntax gives web authors a more flexible and responsive mechanisms to > define the background image position, instead of using fixed values that > need to be adapted to the window's or frame's size. > > *Blink component* > Blink>CSS > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> > > *Web Feature ID* > background-position <https://webstatus.dev/features/background-position> > > *Motivation* > One important motivation is interoperability, given that Chrome is the > only browser that lacks this syntax for the background-position-x/y > longhands. Additionally, the background-position shorthand, which sets both > the x/y positions, already supports the side-relative syntax, so the lack > of the same syntax in the longhands may confuse web developers. There is no > specific explainer, but this MDN page should be enough to understand the > feature: > https://developer.mozilla.org/en-US/docs/Web/CSS/background-position-x > > *Initial public proposal* > None > > *TAG review* > None > > *TAG review status* > Not applicable > > *Risks* > > > *Interoperability and Compatibility* > This feature doesn't imply any interoperability risk, but the contrary, > since Chrome needs to catch up in order to provide the same functionality > than Firefox and Safari. There is no back-compatibility risk, because the > old syntax is still valid if this feature is implemented. > > *Gecko*: Shipped/Shipping > > *WebKit*: Shipped/Shipping > > *Web developers*: Positive (https://issues.chromium.org/issues/40468636) The > issue has 15 votes by now. > > *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* > The feature can be tested and debugged using the regular Chrome DevTools > support (eg, css style inspection) > > *Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* > Yes > https://wpt.fyi/results/css/css-backgrounds/parsing?label=master&label=experimental&aligned&q=background-position-x > > https://wpt.fyi/results/css/css-backgrounds/parsing?label=master&label=experimental&aligned&q=background-position-y > > > *Flag name on about://flags* > None > > *Finch feature name* > None > > *Non-finch justification* > None > > *Requires code in //chrome?* > False > > *Tracking bug* > https://issues.chromium.org/issues/40468636 > > *Estimated milestones* > > No milestones specified > > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5073321259565056?gate=5093327095595008 > > 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5b1b775e-a316-4d59-ab8a-ecbaeef48293n%40chromium.org.
