Re: [csswg-drafts] [css-ui] Change appearance: button to only apply to buttons (#5174)

The CSS Working Group just discussed `Change appearance: button to apply only to buttons`, and agreed to the following:

* `RESOLVED: Limit 'appearance: button' to buttons once we figure out what buttons are`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Change appearance: button to apply only to buttons<br>
&lt;Rossen_> github: https://github.com/w3c/csswg-drafts/issues/5174<br>
&lt;fantasai> florian: General principle that 'auto' does magic by tag, and 'none' turns of magic<br>
&lt;fantasai> florian: But we have some legacy stuff<br>
&lt;fantasai> florian: As specified, appearance: button makes things look like buttons<br>
&lt;fantasai> florian: even when not actually buttons<br>
&lt;fantasai> florian: We could reduce magic of button by only applying 'appearance: button' to buttons<br>
&lt;fantasai> florian: Mozilla was a bit skeptical<br>
&lt;tantek> q-<br>
&lt;emilio> scribenick: emiliop<br>
&lt;emilio> scribenick: emilio<br>
&lt;emilio> fantasai: I think this is one of the things that may be useful to do on things that are not buttons<br>
&lt;emilio> ... for visual reasons it may be useful. In a lot of cases they style it so that they look like their buttons, but if they weren't it would be useful<br>
&lt;iank_> q+<br>
&lt;emilio> ... I don't see a huge benefit from restricting this if we need to make it work for everything else so I'd lean towards not doing that<br>
&lt;fantasai> florian: Current definition allows to turn link into button ...<br>
&lt;emilio> florian: the current definition would allow you to turn stuff into buttons, but also weird cases where they should not<br>
&lt;emilio> q+<br>
&lt;tantek> not sure about the compat details, however I'm in favor of less magic here<br>
&lt;emilio> ack fantasai<br>
&lt;fantasai> florian: but do we reduce this to only compat necessity or do we let people make things into buttons when possible?<br>
&lt;Rossen_> ack iank_<br>
&lt;fantasai> iank_: I think part of the work with the simplifying making appearance sane was to limit the magic in scope<br>
&lt;fantasai> iank_: It seems like a bit of a reversal if we say, actually, we do want these to apply to everything<br>
&lt;fantasai> iank_: so prefer to restrict this down as much as possible<br>
&lt;Rossen_> ack emilio<br>
&lt;fantasai> emilio: If compat allows it, prefer to put less magic here<br>
&lt;fantasai> emilio: We have prefixed appearance, and hacky internal property to support 'appearance: button'<br>
&lt;emilio> s/prefixed/unprefixed, heycam|away implemented it<br>
&lt;fantasai> fantasai: wanted clarification...<br>
&lt;Rossen_> fantasai: are links explicitly called out? can they be used as btn?<br>
&lt;fantasai> florian: Current spec allows any element to look like a button<br>
&lt;fantasai> florian: Chrome says not many people use it, not even on links<br>
&lt;emilio> q+<br>
&lt;Rossen_> ack emilio<br>
&lt;fantasai> emilio: To be clear, magic of 'appearance: button' applies to everything except ? and ?<br>
&lt;emilio> input, textarea and non-listbox selects<br>
&lt;fantasai> iank_: I believe we've already shipped this in 80 which is quite a few releases ago<br>
&lt;fantasai> florian: by this you mean the simplification you proposed?<br>
&lt;fantasai> Rossen_: That means you're not breaking anyone who depends on this?<br>
&lt;fantasai> iank_: Got a few minor reports<br>
&lt;fantasai> iank_: no large-scale breakage<br>
&lt;fantasai> Rossen_: Based on data, we can live with scoping 'appearance: button' to buttons only, is this something we can resolve on?<br>
&lt;fantasai> Rossen_: Proposed resolution is scope 'appearance: button' to buttons only<br>
&lt;fantasai> Rossen_: Hearing no objections. Call it resolved. If there's issue wrt links, I'm sure we can re-oepn<br>
&lt;fantasai> smfr: Are we saying that 'appearance: button' only applies to the BUTTON element?<br>
&lt;fantasai> hober: &lt;input type=button> ?<br>
&lt;fantasai> smfr: file input button?<br>
&lt;fantasai> florian: I guess it's BUTTON and &lt;INPUT type=button><br>
&lt;tantek> and reset<br>
&lt;fantasai> smfr: &lt;input type=submit> ?<br>
&lt;fantasai> florian: Chrome folks can you clarify?<br>
&lt;tantek> Blink folks, what was implemented? &lt;button> &lt;input type=button|submit|reset>?<br>
&lt;fantasai> RESOLVED: Limit 'appearance: button' to buttons once we figure out what buttons are<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5174#issuecomment-666462419 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 30 July 2020 15:33:09 UTC