Last modified: 2013-07-25 07:07:02 UTC
'-moz-border-radius-topleft' '-moz-border-radius-topright' '-moz-border-radius-bottomleft' '-moz-border-radius-bottomright' seem to be unknown properties of Mozilla Firefox I loaded my Watchlist with web console and I got warnings for all of these. My FF version is 16.01
Which site?
The versions with the vendor prefix worked from Firefox 1.0 to 12.0 As long as it also includes border-radius-*, they are harmless (just giving that for firefox 1.0 - 3.x). I don't think Firefox should show errors for vendor prefixes when the standard one is also provided (or it should be optional) but that's what they do.
Introduced in Firefox 13: https://bugzilla.mozilla.org/show_bug.cgi?id=693510
And the documentation page https://developer.mozilla.org/en-US/docs/CSS/border-top-left-radius But I don't think the vendor prefixed versions are really an error.
I wouldn't call them "errors", but "warnings". The error console warns about an "unrecognized rule", just like any other IE specific (filter: alpha(...) ) or -webkit- ones. That particular rule is ignored, and the next rule on the selector is processed. Since it's now unsupported by Firefox, it's probably a good idea to get rid of them, and at the same time make sure that the standard and unprefixed border-radius are present.
Same for -moz-opacity -moz-box-shadow -moz-text-shadow while loading the Main page
Gerrit change #46281
Removing the vendor properties will surely get rid of the console errors but that will at the same time break the layout for Firefox version 12 and below. According to our October 2012 browsing statistics at http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm there was still a good amount of Firefox v 12 and below. Even if Firefox 3.6 was "just" 1.27% of the HTML pages view, that was still 350Millions views on October 2012 We could potentially serve a different CSS stylesheet depending on the browser version but that makes everything much more complicates and slightly grow our caching needs.
What are you talking about when you say "break the layout"? That sounds a bit exaggerate ;) I agree we're still supporting Internet Explorer 6.0, but here we're talking about rounded borders, opacity and shadows. In fact, we're talking only about rounded borders and shadows, because opacity is supported since Firefox 0.9 [1]. They're not a critical feature and I don't feel this would cause any layout issues at all, like misalignments or things like that. ---- [1] https://developer.mozilla.org/es/docs/CSS/opacity
The same argument hold for the console warnings in Firefox 12 :-] It is not really important to have CSS warnings in FX 12, nobody cares about it but the developers =)
I think the bug should be solved in the console side, adding an option (or just making it the default), not warning about a vendor-prefixed property if followed by an standard one.
