5 ms·
What you, as Web developers, can do, is use Firefox while developing your site to ensure it really works well on non-Chromium browsers. And do your level best t
by roca 7y ago
What you, as Web developers, can do, is use Firefox while developing your site to ensure it really works well on non-Chromium browsers. And do your level best to encourage your developer friends to do the same. If they're on Mac and would rather use Safari, that'll do too.
Then, every time you see any site or any Web developer satisfied with "works in Chrome", do what you can to let them know that's not acceptable. In a polite, loving, and extremely firm manner of course.
- tomjen3 7y agoA decent idea of course, but you are going to run in to the same issue as everybody else who tries that: unless Firefox has a significant market share, it is just not worth throwing resources after it. What you can do is develop automatic filters to make chrome specific CSS prefixes general, etc. Those are probably worth using since a few hours/days of engineering time easily is worth the larger market share.
- roca 7y agoFirefox already implements a bunch of -webkit prefixed features for compatibility reasons. Are there specific Chrome-only features that aren't yet supported that you think should be? If so, file Firefox bugs!
- stOneskull 7y agoGotta help get the user base bigger