Web-Facing Change PSA: Relax <select> parser

[Joey Arhar]

Contact emails

jar...@chromium.org

Specification

https://github.com/whatwg/html/pull/10557

Summary

This change makes the HTML parser allow additional tags in <select> besides <option>, <optgroup>, and <hr>. This change is in support of the customizable <select> feature but is being shipped first because it can be done separately and has some compat risk which I'd like to get feedback on. Customizable select explainer: https://open-ui.org/components/customizableselect/

Blink component

Blink>HTML>Parser

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1086)

   Positive of experimenting: https://github.com/whatwg/html/issues/10310#issuecomment-2189178702

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/414)

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?

None

Debuggability

None

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 chrome://flags

SelectParserRelaxation

Finch feature name

SelectParserRelaxation

Requires code in //chrome?

False

Tracking bug

https://crbug.com/335456114

Estimated milestones

Shipping on desktop	130
DevTrial on desktop	128
Shipping on Android	130
DevTrial on Android	128
Shipping on WebView	130

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/5130601930424320?gate=5195708819570688

This intent message was generated by Chrome Platform Status.

[Domenic Denicola]

Can you explain more why you think a web-facing change PSA, instead of an Intent to Ship, is appropriate for this feature? In particular, the lack of discussion of compat and interop risks is concerning.

--
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/CAK6btw%2Bxjhnd%2BLtAfx%2B3x_bsXpyQH5W3JDEv57T3WDtXQns1cA%40mail.gmail.com.

[Joey Arhar]

Good point. I re-filed this as an intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/5_9-Qkvlj2M