Intent to Deprecate: Remove non-standard appearance keywords

[Di Zhang]

Contact emails

dizh...@chromium.org

Explainer

None

Specification

https://drafts.csswg.org/css-ui-4/#appearance-switching

Summary

Since only standard appearance keywords should be supported, we are removing the appearance (and -webkit-appearance) keywords that are only meant to be used internally: * inner-spin-button * media-slider * media-sliderthumb * media-volume-slider * media-volume-sliderthumb * push-button * searchfield-cancel-button * slider-horizontal * sliderthumb-horizontal * sliderthumb-vertical * square-button Note that value slider-vertical will not be removed as part of this patch it is used for allowing <input type=range> vertical. It will be removed once feature FormControlsVerticalWritingModeSupport is enabled in stable. [1] https://drafts.csswg.org/css-ui-4/#appearance-switching [2] https://github.com/w3c/csswg-drafts/issues/8506#issuecomment-1515062326

Blink component

Blink>CSS

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

This feature only affects the reflection in computed style. Currently, while it is possible to set an appearance value with one of these non-standard values, it will not affect the appearance of that element. Now, if appearance is set to one of these non-standard values, the returned computed appearance value will be auto. It is unlikely websites depend on this information: this deprecation should be web compatible.

Gecko: Shipped/Shipping

WebKit: No signal

Web developers: No signals

Other signals:

Ergonomics

There are no other platform APIS this will be used in tandem with and this will not make it hard for chrome to maintain good performance.

Activation

There should be no challenge for developers to take advantage of this feature immediately.

Security

N/A

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 non-standard appearance values we are removing are already not listed in the autocomplete in DevTools.

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?

Yes

Flag name on chrome://flags

RemoveNonStandardAppearanceValue

Finch feature name

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=924486

Estimated milestones

DevTrial on desktop

115

DevTrial on Android

115

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

This intent message was generated by Chrome Platform Status.

[Di Zhang]

Replaced this Intent to Ship with correct/better email: https://groups.google.com/a/chromium.org/g/blink-dev/c/gfxScdL8O3g