Intent to Ship: Ship anchor-visible and anchor-valid, and deprecate the plural versions

[Mason Freed]

Contact emails

mas...@chromium.org

Explainer

No information provided

Specification

https://drafts.csswg.org/css-anchor-position-1/#position-visibility

Summary

The CSSWG resolved to rename `anchors-valid` --> `anchor-valid` [1] and `anchors-visible` --> `anchor-visible` [2]. To accomplish this, we'll rename the properties to the singular variants, and add aliases from the plural versions to the singular versions. At a later date, we will remove the plural variants. This chromestatus is only about shipping the new versions, and deprecating the old ones (but not removing them).

[1] https://github.com/w3c/csswg-drafts/issues/10201#issuecomment-4180411971 [2] https://github.com/w3c/csswg-drafts/issues/10201#issuecomment-4390233490

Blink component

Blink>CSS

Web Feature ID

anchor-positioning

Motivation

CSSWG resolved to rename, and to maintain baseline status for anchor positioning, Chrome needs to ship the new names.

Initial public proposal

No information provided

Search tags

position-visibility, anchor-visible, anchor-valid

TAG review

N/A

TAG review status

Not applicable

Goals for experimentation

None

Risks

Interoperability and Compatibility

Since this is the shipment of new names, and not the removal of the old names, there should be no compat risk. Shipping the new names improves interop.

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?

No information provided

Debuggability

No information provided

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

Yes

Is this feature fully tested by web-platform-tests?

Yes

Flag name on about://flags

No information provided

Finch feature name

PositionVisibilitySingularValues

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/526682332

Estimated milestones

Shipping on desktop	157
DevTrial on desktop	157
Shipping on Android	157
DevTrial on Android	157
Shipping on WebView	157

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).

No information provided

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5136123851571200?gate=6099968887750656

This intent message was generated by Chrome Platform Status.

[Chris Harrelson]

LGTM1

--
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/CAM%3DNeDgweujYo5vGyb7yT7HrcEzph53C%2BEfTNx7rRteg3ky_0Q%40mail.gmail.com.

[Mike Taylor]

LGTM2

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_EdnedCqVZ3GabE2w3JzcY2Yosx1ZpSmKei_-YrhTQfA%40mail.gmail.com.

[Vladimir Levin]

LGTM3

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/95795719-829e-4181-be47-a6d16ee3a62e%40chromium.org.