Skip to content

[css-ui] Remove warning about 'appearance' #3969

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

[css-ui] Remove warning about 'appearance' #3969

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 0 additions & 35 deletions css-ui-4/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1749,41 +1749,6 @@ so this specification allows flexibility.

<h3 id="appearance-switching" caniuse="css-appearance">Switching appearance</h3>

<div class=issue>
<strong>This is a work-in-progress, not cleared for shipping</strong> (see <a href="https://github.com/w3c/csswg-drafts/issues/1250">Github issue 1250</a>).

This previously existed as a prefixed form in most browsers.
Before standardization, in addition to none,
the possible values were a very long list of all the ways an element could look;
each value being responsible for giving form control their specific look and feel.
This list was different across browsers.

We concluded this was impractical to standardize,
in part because many apply to pseudo-elements that other browsers don't have,
as they construct form elements differently,
and which should not be standardized,
since the ability to make for controls look substantially different on different platforms
should be preserved.

Also, because the ability to turn any arbitrary element (including any form control)
into any (other) arbitrary form control
is considered a misfeature.

Instead, we'd just have an "auto" value that makes form controls look like whatever they need,
and a "none" value that suppresses "native" look.

However, there is evidence that this alone is not web compatible,
due in part to uses such as:
<pre><code highlight=css>
input { appearance: none; }
input[type=checkbox] { appearance: checkbox; }
</code></pre>

This Work-In-Progress specification is a compromise between the two,
preserving the simplicity of the ''none | auto'' model
while maintaining compatibility with existing content.
</div>

While the way most elements in a document look can be fully controlled by CSS,
form controls are typically rendered by UAs using native UI controls of the host operating system,
which can neither be replicated nor styled using CSS.
Expand Down