The feature enables custom elements to expose their states via :state() CSS pseudo class.
Built-in elements have certain “states” that can change over time depending on user interaction and other factors, and are exposed to web authors through pseudo classes. For example, some form controls have the “invalid” state, which is exposed through the :invalid pseudo class.
Like built-in elements, custom elements can have various states to be in too, and web authors want to expose these states in a similar fashion as the built-in elements.
No compatibility risk. This is a new feature, and won't break existing behavior.
Low interoperability risk. Other browser vendors participated in the standardization discussion, and they didn't oppose.
Firefox: No public signals
Edge: No public signals
Safari: No public signals
Web developers: Positive (https://github.com/w3c/webcomponents/issues/738)
This feature is a part of Custom Element API. We don't think this could make it hard for Chrome to maintain good performance.
It's hard for developers to apply this feature until all major browsers ship it. It's difficult to make a polyfill for this feature.
None. This feature has no security implication.
You do not have permission to delete messages in this group
Report message as abuse
Sign in to report message as abuse
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to TAMURA, Kent, blink-dev
Just want to add to the "Interoperability" point here, most recently this proposal was discussed in the TPAC 2019 WebComponents session (minutes here, it's the first topic discussed - search for "custom state").
Mozilla & Apple representatives, plus a few web devs were there and engaged in the discussion quite positively. In addition to the discussions before (in the issue and previous F2Fs), "No public signals" listed above is probably a bit conservative :)