W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

[csswg-drafts] [CSS-appearance] Should we not use it, for now?

From: Jitendra Vyas via GitHub <sysbot+gh@w3.org>
Date: Tue, 14 Nov 2017 10:15:08 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-273735944-1510654507-sysbot+gh@w3.org>
jitendravyas has just created a new issue for https://github.com/w3c/csswg-drafts:

== [CSS-appearance] Should we not use it, for now? ==
I'm working on a website and ran CSS validation on its CSS. They only validation error (not warning) I have is about `appearance`. I was using it give custom look to `<select>` to match it with design file. 

![w3c css validator results f](https://user-images.githubusercontent.com/77309/32773917-bda93434-c950-11e7-8351-15f3c4ae5380.png)

And It's available in [non-vendor-prefixed ]( https://css-tricks.com/almanac/properties/a/appearance/)(Also knows as standard) too.

I found some discussion about it but not sure what is the current recommendation from W3C for now.
https://drafts.csswg.org/css-ui-4/#appearance-switching
https://github.com/w3c/csswg-drafts/issues/1250

Should I not use it for now 1) because Validator caught it as invalid and 2) there is a possibility that it can be abandoned like @apply http://www.xanthir.com/b4o00 later.



Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1982 using your GitHub account
Received on Tuesday, 14 November 2017 10:15:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 November 2017 10:15:15 UTC