That message is more for the Mozilla community than for the outside world. If Firefox for iOS implements WebRTC on top of Webkit, for example, that&#x27;s a clear win for users. So Mozilla (the company) decided it&#x27;s worth their money to make a Webkit browser and try to improve the situation on iOS little by little. But Mozilla (the community) is full of people with very strong ideas of the direction they want the organization to take, so the immediate reaction is for them to reject the idea – even core contributors. &quot;Firefox without Gecko is not Firefox!&quot;. Instead of arguing whether branding a Webkit shell as Firefox is too big of a compromise, Mozilla (the leaders) redefines what the brand is about.<p>This might seem silly, but it has a big impact on the community, by making it clear what the goals of the project are, and hopefully eliminating all the bikeshedding on what is and isn&#x27;t Firefox.<p>EDIT: I guess I never answered your question: open Web standards are still a priority for Mozilla, it&#x27;s just that we&#x27;ve decided the little benefit for the user we can create by writing Firefox for iOS is also a priority.