[css-ui] Define "native appearance" and rename control to widget #3991
Conversation
css-ui-4/Overview.bs
Outdated
| <a>controls</a> are typically rendered by UAs using native UI controls of the host operating system, | ||
| which can neither be replicated nor styled using CSS. | ||
|
|
||
| The term <dfn>control</dfn> denotes the following [[HTML]] elements: |
There was a problem hiding this comment.
Is it good to be quite this specific? What if things change? Are there disagreements even on some in terms of support? Could you say instead "Examples of controls in HTML are: ....."
There was a problem hiding this comment.
This definition, like the spec itself, is meant to be canonical. Ideally, if things change, they'd start by changing here. Even if we find ourselves updating the definition reactively, it seems to me that completeness is a goal of the standard. From that perspective, suggesting a partial list is less helpful than defining a complete set.
There was a problem hiding this comment.
is <summary>/<details> not a control then?
There was a problem hiding this comment.
Good question! I'll defer to the editor on that.
There was a problem hiding this comment.
I'm thinking that maintaining this in a css spec is the wrong place. Tracking how the HTML spec changes will never be perfectly synchronized. Ideally, we'd just refer to a term defined in the HTML spec, and they'd update it when they add new elements. However, there doesn't seem to be one already.
There was a problem hiding this comment.
Ideally, we'd just refer to a term defined in the HTML spec
Doesn't the existing term widget satisfy this criteria? BTW, it already includes <details>.
…rename 'control' to 'widget'
|
I have changed this PR and whatwg/html#4857 as per discussion in that PR. Please review. |
control #3990|
Not sure why the IPR checker is stuck, all contributors to this PR are good to go, so I'll merge anyway. |
[css-ui] Define
control#3990