Skip to content

[css-ui-4] Define appearance:base #10691

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

Merged
merged 9 commits into from
Sep 17, 2024
Merged
Changes from all commits
Commits
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
37 changes: 36 additions & 1 deletion css-ui-4/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -2111,7 +2111,7 @@ Switching appearance: the 'appearance' property</h3>

<pre class="propdef">
Name: appearance
Value: ''appearance/none'' | ''auto'' | <<compat-auto>> | <<compat-special>>
Value: ''appearance/none'' | ''auto'' | ''base'' | <<compat-auto>> | <<compat-special>>
Initial: none
Applies To: all elements
Inherited: no
Expand All @@ -2135,6 +2135,22 @@ Switching appearance: the 'appearance' property</h3>
giving them a <dfn export>primitive appearance</dfn>
where CSS can be used to restyle them.

Using ''appearance: base'' gives <a>widgets</a> a <dfn export>base
appearance</dfn>. <a>Widgets</a> in <span>base appearance</span> have their
<a>native appearance</a> suppressed where CSS can be used to restyle them,
just like <a>primitive appearance</a>, but also have default styles which are
usable and interoperable. This is unlike <a>primitive appearance</a> which
can cause some <a>widgets</a> to disappear completely.

A widget can have some style sheet associated with it and those styles can
change based on whether the widget has a <span>base appearance</span>.
<span>Native appearance</span> and <span>primitive appearance</span> should
have the same styles.

ISSUE: ''appearance:base'' is not ready to ship until its stylesheet has been
fully defined in the HTML specification, and implemented accordingly, for all
HTML form controls.

<details class=note>
<summary>Note on the history of this feature</summary>

Expand Down Expand Up @@ -2199,6 +2215,25 @@ Switching appearance: the 'appearance' property</h3>

Elements other than <a>widgets</a> must be rendered as for ''appearance/none''.

<dt><dfn>base</dfn>
<dd>
The effect of ''appearance/base'' depends on the element it is applied to:
<dl class=switch>
: elements other than <a>widgets</a>
:: Elements other than <a>widgets</a> must be rendered as for
''appearance/none''.

: <a>Widgets</a> which support <a>base appearance</a>
:: Just like ''appearance/none'', the element is rendered following the
usual rules of CSS. <a>Widgets</a> must not have their <a>native
appearance</a>, and instead must have their <a>base appearance</a>.

: <a>Widgets</a> which don't support <a>base appearance</a>
:: <a>Widgets</a> which don't have a <a>base appearance</a> must be
rendered as for ''appearance/auto''. The host language is responsible
for defining which <a>widgets</a> have a <a>base appearance</a>.
</dl>

<dt><dfn type="">&lt;compat-auto></dfn>
<dd>
These values exist for compatibility of content developed
Expand Down