-
Notifications
You must be signed in to change notification settings - Fork 708
[css-ui-4] Clarify that 'appearance: none' causes an element to not be replaced anymore #1018
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
Comments
This seems a priori reasonable to me, but we (I?) should probably go through all the form elements and see if that actually works out. Specifically, I am wondering about complex form controls whose sub-components cannot just boil down to CSS styling. |
@zcorpan , do you have any insight into this? |
Form controls aren't really replaced elements, though they share some traits with replaced elements. For example, buttons https://html.spec.whatwg.org/multipage/rendering.html#button-layout
but it needs to act as a non-replaced element for the purpose of baseline alignment when it's Whether those traits are removed by |
Related to this issue, according to https://bugs.chromium.org/p/chromium/issues/detail?id=480891#c24 the usage count for So there is obviously a need to define this. Some related discussion already happened in https://lists.w3.org/Archives/Public/www-style/2016Mar/0190.html. Sebastian |
The description of the
none
value of theappearance
property currently says this:It doesn't explicitly state that it turns form controls into non-replaced elements.
Sebastian
The text was updated successfully, but these errors were encountered: