Bravo! As a Firefox user, the trend of web developers only testing in Chrome (and ending up using features that only work in Chrome) is getting really annoying. Most of the time, the fixes are really simple, like including more prefixes than -webkit.

Very happy to see Mozilla raising awareness around this issue.

Personally, I have Firefox and Chrome open side by side for development. If those two work, Safari and Edge generally will too. I'll add IE specific rules/hacks afterward.

skrowl

If your app only works in Webkit / Blink, you've written a Chrome App and not a Web App.

Your CUSTOMERS do not want to see "To use this site / app, stop using the web browser you've chosen to use (or your company has chosen for you) and go install this instead!"

nathancahill

Here's a thought exercise: how will this trend be exacerbated by the Electron/Chromium stack? Should Mozilla develop a competing engine for "native" apps?

latortuga

Mozilla actually had one for years, called XULRunner.

dfabulich

It's not good; people use Electron instead of XULRunner because XULRunner was barely maintained. It would randomly stop working on major Firefox releases, and would stay broken for weeks, because nobody noticed or cared that XULRunner didn't work, as long as core Firefox kept working.

Even when it did work, working with XPCOM sucked.

Positron https://github.com/mozilla/positron is the new XULRunner. WIP, doesn't actually work yet. :-(