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/ I did a compat analysis and determined that the vast majority of sites which would see the effects of the parser changes would not have their behavior changed. More details here: https://github.com/whatwg/html/issues/10310 If there are major issues with this change, I will reassess and make adjustments to the parser as needed.
I believe there is low interop risk because other vendors are reviewing the proposal in WHATWG and are not objected to changing the parser behavior here. There is a compat risk if websites are relying on the old parser behavior. As I mentioned in the main description, I have done an analysis and based on the websites I have investigated I believe there is low risk. If we encounter issues then I will adjust the parser as needed.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
Shipping on desktop | 130 |
DevTrial on desktop | 128 |
Shipping on Android | 130 |
DevTrial on Android | 128 |
Shipping on WebView | 130 |
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).
NoneContact emails
jar...@chromium.org
Explainer
https://open-ui.org/components/customizableselect
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/ I did a compat analysis and determined that the vast majority of sites which would see the effects of the parser changes would not have their behavior changed. More details here: https://github.com/whatwg/html/issues/10310 If there are major issues with this change, I will reassess and make adjustments to the parser as needed.
Blink component
Blink>HTML>Parser
TAG review
None
TAG review status
Pending
Risks
Interoperability and Compatibility
I believe there is low interop risk because other vendors are reviewing the proposal in WHATWG and are not objected to changing the parser behavior here. There is a compat risk if websites are relying on the old parser behavior. As I mentioned in the main description, I have done an analysis and based on the websites I have investigated I believe there is low risk. If we encounter issues then I will adjust the parser as needed.
Gecko: 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 (https://github.com/mozilla/standards-positions/issues/1086)
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).
NoneLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5145948356083712?gate=5114873999261696
This intent message was generated by Chrome Platform Status.
--
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%2B2u4-MY3c2x5uci_dOJWw8UdDNGfr_BiSfNESQwmPh5w%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
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%2B2u4-MY3c2x5uci_dOJWw8UdDNGfr_BiSfNESQwmPh5w%40mail.gmail.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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/304f1ceb-9cdf-4b8e-8d1b-4fa540a1eae4n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_w1KxLGL9FDs6tiYXzYKduxWMcnUwFmcs_s4JadtXQWg%40mail.gmail.com.