-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
appearance
#884
Comments
Is this about trying to get interoperability for |
I believe it's about the "act like |
This was proposed in the Form Controls focus area for Interop 2022 (see #11), but the kind-of-widget* tests weren't included then. (Maybe the tests landed in wpt too late, I'm not sure.) |
Thank you for proposing We are pleased to let you know that this proposal was accepted as part of the Web Compat focus area. You can follow the progress of this focus area on the Interop 2025 dashboard. For an overview of our process, see proposal selection. Thank you for contributing to Interop 2025! Posted on behalf of the Interop team. |
Description
CSS UI 4 defines a set of properties that disable native appearance. This behavior is currently tested via WPTs in
css/css-ui/compute-kind-widget-generated
[1].Currently browsers are not consistent about disabling native appearance when these properties are set, or incorrectly modify the computed style of an element that retains native appearance [2].
[1] https://wpt.fyi/results/css/css-ui/compute-kind-widget-generated?label=experimental&label=master&aligned
[2] w3c/csswg-drafts#9919
Specification
https://drafts.csswg.org/css-ui-4/#appearance-disabling-properties
Additional Signals
No response
The text was updated successfully, but these errors were encountered: