And I still see web developers who reject the idea that we have troublesome webkit monoculture. And when you ask them what non-webkit browsers they are testing on, they're response while not literally "What do you mean testing?", effectively conveys the same: "Just use latest Chrome (Works on my machine)".<p>When Microsoft created its initial version of ASP.Net, it was mainly designed to allow Windows VB6 point-and-click programmers to create web applications without understanding how the web worked. It was a joke of a web-framework.<p>The irony is that right now, I can tell the current crop of "ninja" web-developers (who rightfully rejected ASP.Net and its ilk) are starting more and more to look like this generation's VB6 programmers: Unambitious. Untalented. Unprincipled. Web-standards? Whatever works, and this works on my machine.<p>It's quite frightening. I thought we were past this shit.
FWIW, these aren't actually enabled in 46 unless you flip the `layout.css.prefixes.webkit` pref to true.<p>(We hope to flip that to true by default soon: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1259345" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1259345</a>)
Very interesting considering WebKit is moving away from prefixes: <a href="https://webkit.org/blog/6131/updating-our-prefixing-policy/" rel="nofollow">https://webkit.org/blog/6131/updating-our-prefixing-policy/</a>
I don't blame them. I remember reading how IE on Windows 10 sends a Safari user agent because so many sites use user agent sniffing rather than capability detection for things like touch events.<p>So, all disappointing, but we (as an industry) have no-one but ourselves to blame for it. Firefox and MS are just putting the user first.
Disappointing, but you can see the corner they're wedged into here. Maintain purity or lose users due to sites not working "because of Firefox".
This is why we can't have nice things. <a href="https://webkit.org/blog/6131/updating-our-prefixing-policy/" rel="nofollow">https://webkit.org/blog/6131/updating-our-prefixing-policy/</a>
This specification, created by Mozilla, is also relevant: <a href="https://compat.spec.whatwg.org/" rel="nofollow">https://compat.spec.whatwg.org/</a>
FWIW, Firefox Dev Ed / Aurora has had this for a while and has been on 47 since 08 March.<p><a href="https://www.mozilla.org/en-US/firefox/47.0a2/releasenotes/" rel="nofollow">https://www.mozilla.org/en-US/firefox/47.0a2/releasenotes/</a>
Google is moving as aggressively as Microsoft was with IE, and Mozilla bent over, again.<p>for the kids that don't remember, go read about why all the worst parts of JavaScript are the way they are...
> Firefox 46 supports some -webkit prefixed CSS properties<p>>When implementing new features for the Web, it’s important for us to be able to get them into the hands of developers early, so they can give new things a try<p>> WebKit is moving away from prefixes (webkit.org)<p>Well done Mozilla.