Skip to content
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

Closed
pxlcoder opened this issue Oct 10, 2024 · 4 comments
Closed

appearance #884

pxlcoder opened this issue Oct 10, 2024 · 4 comments
Labels
accepted An accepted proposal focus-area-proposal Focus Area Proposal

Comments

@pxlcoder
Copy link

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

@pxlcoder pxlcoder added the focus-area-proposal Focus Area Proposal label Oct 10, 2024
@pxlcoder pxlcoder changed the title appearance appearance Oct 10, 2024
@jensimmons
Copy link
Contributor

Is this about trying to get interoperability for appearance: none?

@zcorpan
Copy link
Member

zcorpan commented Oct 24, 2024

I believe it's about the "act like appearance: none when there's an author property set for these properties"

@zcorpan
Copy link
Member

zcorpan commented Oct 24, 2024

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.)

@wpt-interop
Copy link
Collaborator

Thank you for proposing appearance for inclusion in Interop 2025.

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.

@foolip foolip added the accepted An accepted proposal label Feb 17, 2025
@foolip foolip closed this as completed Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted An accepted proposal focus-area-proposal Focus Area Proposal
Projects
Status: Done
Development

No branches or pull requests

5 participants