Evidence shows that they don't, and that developers are absolutely not going back and fixing code they shipped years ago, so all the principled stance nets firefox is "firefox breaks <outlook mobile>, it works just fine in chrome, screw that piece of shit firefox".
I opened a ranty support request about the fact that they should consider replacing their web devs if they were unable to create a site that adhered to standards enough that they didn't feel the need to write browser specific code.
Having spent some time in the past few years doing web development myself, I don't feel the least bit sorry for web developers that are using browser specific prefixes, or other crap. In my experience its actually chrome that has serious rendering bugs these days, and FF/IE manage to render pages pretty similarly. So, at this point if your a web developer using chrome as your default target, that should be considered incompetence.
Let's heap some scorn on those websites and internal corporate teams that do all their work on Chrome and Safari and never test on other browsers. It's always laziness (not testing their crap at all) or lame excuses (Chrome is faster, why would I bother?) that's to blame.
I don't mind being the "Firefox guy" on teams I'm part of and making sure my baby always gets some love.
The so-called 'standards' have been dead since Google forced to rubber-stamp the SPDY protocol as HTTP2.
We're gonna have to learn to live in a world where the Internet is owned by Google.
If firefox doesn't support -webkit prefix, the developers are forced to consider the compatibility issues and use something like "autoprefixer" to help. All of the experimental features will work as well as they could on different browsers (IE, Chrome, Firefox...)
But if firefox support -webkit prefix and the developers buy it, they will write something like '-webkit-feature' directly and assume it will work on the major browsers. The problem is, major browsers only includes webkit based browsers, what about IE ?
If a developer uses a non-standard feature directly, forcing he/she to consider the potential problems is better than leaving him/her a fragile solution.