Diversifying the income seem to be an important goal right now, even if the userbase hasn't been very sympathetic so far.
Would you mind to expand a bit about "vague and baseless"? Or maybe you could spend some time and learn the history of canvas element, or CSS transforms?
http://lists.w3.org/Archives/Public/www-style/2007Nov/0080.h...
http://lists.w3.org/Archives/Public/www-style/2007Nov/0090.h...
http://lists.w3.org/Archives/Public/public-whatwg-archive/20...
As for "all new WebAPI's" you'd be surprised how many of them were first implemented in WebKit. WebRTC? Chrome—fall 2012. Firefox—summer 2013
Enlighten us: https://wiki.mozilla.org/WebAPI
WebRTC? Chrome—fall 2012. Firefox—summer 2013
I don't think so: https://hacks.mozilla.org/2012/11/progress-update-on-webrtc-...
Note that at this point Firefox had DataChannel, and it would take Chrome months to catch up there. Firefox also introduced the used audio codec.
That said it's a bad example, because WebRTC standardization is currently a strong effort between both companies and it'd be great for the web if more standards went this way rather than ending up with having to try to standardize half-assed implementations from one rendering engine. (cough WebSQL cough)
They are no bs, fight for internet freedom, celebrate transparency, are the centroid of internet activism and the extension of Aaron Schwartz' ideas. Mozilla is what makes me want to stay in tech and every company should try to learn from Mozilla what it means to be a tech company.