Remove -webkit-box-shadow

[morganestes]

Adoption of box-shadow by browsers is pretty high, and -webkit- hasn't been needed on it since Safari 5.0 (see ​http://beta.caniuse.com/#feat=css-boxshadow)

It's time. Less rules == faster loads.

[morganestes]

#26919 was marked as a duplicate.

[bassgang]

Replying to SergeyBiryukov:
Should we still wait until this ticket is reviewed or does your latest Version change mean: "Go for it"?

[helen]

Replying to bassgang:

Replying to SergeyBiryukov:
Should we still wait until this ticket is reviewed or does your latest Version change mean: "Go for it"?

You don't really need to wait for anything to create a patch. However, note that the version field is not the same as the milestone. Version indicates the earliest affected by a bug or the point where a feature/enhancement was proposed.

I have two things here: one, that I think I would rather handle this through Grunt and Autoprefixer, and the other is that I'm wondering if this is a result of our support for the Kindle browser. Having a hard time finding a definitive resource on it, only vague statements that it's sort-of Android 2.3's browser (which needs -webkit-); any pointers appreciated.

[bassgang]

Replying to helen:

You don't really need to wait for anything to create a patch. However, note that the version field is not the same as the milestone. Version indicates the earliest affected by a bug or the point where a feature/enhancement was proposed.

Thanks for clarification.

I have two things here: one, that I think I would rather handle this through Grunt and Autoprefixer, and the other is that I'm wondering if this is a result of our support for the Kindle browser. Having a hard time finding a definitive resource on it, only vague statements that it's sort-of Android 2.3's browser (which needs -webkit-); any pointers appreciated.

​http://en.wikipedia.org/wiki/Kindle_Fire says that the Kindle Fire is "based on Android OS 2.3.3", so if WordPress currently supports this device, we should not remove the -webkit prefix.

Moving the -webkit prefix into a grunt-autoprefixer task sounds good for me.

Kindle ​HD and ​HDX are both based on Android OS 4.2.2 according to Wikipedia, so for both of them we do not need the prefix.

[drozdz]

Proposed patch for #26916

[morganestes]

Okay, so "kill it with fire" may not be the best move if we're trying to support Kindle, but it may be a non-issue all around if we're going to use Grunt and Autoprefixer. Remove them from the current styles and let Grunt handle it if we need to support Kindle.

For the record, Amazon's ​Silk Developer Guide states that the browser "supports basic CSS3 features like backgrounds, opacity, rounded corners, and text effects, as well as other features" but doesn't mention box-shadow specifically. However, this ​Modernizr issue on GitHub has a bit more insight as to what is usable.

[nacin]

I tested this on an original Kindle Fire and box-shadow wasn't supported.

At this point, this is a duplicate of #27078.