Earlier quoted context omitted.
This was tough for us, because we're big believers in the standards-based web. We 100% promise that all the code we generate works across all browsers. Unfortunately, while most of the editor works in all browsers, getting full support is really hard. We're doing a lot of things that get pretty deep in the browser, so we wanted to lock things down as much as possible. We almost were electron-only to ensure consistenc…
As a basically-everything-except-Chrome user, I'm increasingly skeptical of excuses this. There's almost certainly some feature(s) that you've spent a lot of time on that provide less value than having the app working in Firefox and Safari. As soon as I saw it was Chrome only, I closed out.
On the other hand think of it from their perspective if you want your odds of success to be higher you have to focus on the biggest user base, simple 80/20. I doubt that an additional feature vs friefox support is a fair comparison.