Twenty Thirteen: Typo in browser prefix

[Jayjdk]

There's a small typo in the -moz prefix for in .site-header .searchform .field

Patch attached.

However, is some of the prefixes still necessary? Firefox has supported stuff like transition without a prefix since version 16. How long back is the theme supporting the different browsers? Because there's a whole lot more prefixes that could be removed - not just for Firefox.

[lancewillett]

Let's discuss the vendor prefix support in Twenty Thirteen office hours -- see ​http://make.wordpress.org/core for the times. Tomorrow is the next at 17 UTC.

I think we should support a few versions back but am open to suggestions and best practices. We should match our support for older browsers, and also agree that as long as the fallback isn't "broken" and looks good we can get rid of prefixes for properties that the most recent stable version of each browser implements fully.

[lancewillett]

Oh, and thank you for the ticket and patch. :)

[lancewillett]

In 23464:

Twenty Thirteen: fix typo in browser transition prefix. Fixes #23568, props Jayjdk.

[lancewillett]

Based on notes in today's Twenty Thirteen office hours, we're going to take the following approach:

• Look at each browser's prefix support. If it's been dropped in the stable version in the last year, we can remove it.
• Keep in mind a webkit prefix may be needed for older mobile devices (​http://isandroidgoodyet.com/).
• We should mention here in the ticket notes that the theme itself may need to fail gracefully.

[Jayjdk]

Should it be in this ticket or a new one?

[lancewillett]

Go ahead and make a new one -- just change the title a bit, maybe "audit and clean up browser prefixes" or something.

[Jayjdk]

New ticket: #23582