Support "appearance"?

[tobiastom]

I see that appearance is not supported equally through different browsers, but maybe at least some

appearance: none
-webkit-appearance: none
-moz-appearance: none

support would be nice?

[ai]

There are 2 problem with appearance:

1. It is non-standard vendor specific property. There is no any current W3C reccomendation about this property.
2. There is no Can I Use page.

I think that not there is no appearance, only vendors -webkit-appearance and -moz-appearance. Like non-standard webkit-tap-highlight-color or -webkit-touch-callout. So I prefer just write:

-webkit-appearance: none
-moz-appearance: none

What do you think about this property?

[tobiastom]

Yeah, as I mentioned I'm at least aware of your first point. The second point makes it even worse…

Not sure. I though implementing only appearance: none and translating it to the related rules would be ok. Now I'm not really sure anymore.

There is an issue in caniuse itself (Fyrd/caniuse#42), also without much activity.

[ai]

We now have updater.all, so we can implement it without Can I Use support. I reopen issue.

[ai]

But is -moz-appearance is really used now?

[porada]

To answer @ai’s question, Normalize.css uses the property a few times.

I wouldn’t allow appearance to be autoprefixed because:

1. There is no such thing as unprefixed appearance, and there probably won’t be. Converting appearance to -moz-appearance and -webkit-appearance makes it a mixin—a mixin that you can create yourself.
2. The same values for both properties might mean different things for the two browsers. And most of the times, you just target one (e.g. in a vendor prefixed pseudo-element that doesn’t have to be applied for the second browser).

[ai]

Agree. Close again :-).

[Grawl]

I just figured that Safari and Chrome in iOS 6 doesn't render inset box-shadow on inputs until -webkit-appearance: none is specified. What situation in Firefox Mobile?

[porada]

Still not a case for autoprefixing.

[Grawl]

Okay. But there is W3C Recommendation about appearance.

[ai]

@Grawl it is outdated spec, new revision doesn‘t contain appearance.

As I understand, in FF you can remove box-shadow by box-shadow CSS. So in your case it is only -webkit-appearance: none is needed.

[Grawl]

@ai I don't need to remove box-shadow. I need to apply it to input.