I'm mostly lazy and generally build just for Chrome, if it doesn't work on others I will consider fixing it if
1) I notice
2) The browser is notable enough (basically Firefox, maybe for Edge)
3) It's easy enough to fix
4) The breakage is significant
If you're trying to show off your skill with your projects you should put extra care on compatibility, documentation, and other such details that matter for released products. If you're just building for yourself, you can let others worry about their problems.
I've been starting of thinking more about Brave recently, as it seems to have a lot of potential to becoming a significant player in the market, but since it's Chromium in the base I probably don't need to do any special tests for it. I would probably really consider it if I was doing anything like video, audio, or other such stuff where available codecs matter and might differ between browsers.
I'm mostly lazy and generally build just for Chrome, if it doesn't work on others I will consider fixing it if
1) I notice
2) The browser is notable enough (basically Firefox, maybe for Edge)
3) It's easy enough to fix
4) The breakage is significant
If you're trying to show off your skill with your projects you should put extra care on compatibility, documentation, and other such details that matter for released products. If you're just building for yourself, you can let others worry about their problems.
Microsoft provides free VM images for testing their browsers: developer.microsoft.com/en-us/micr...
I've been starting of thinking more about Brave recently, as it seems to have a lot of potential to becoming a significant player in the market, but since it's Chromium in the base I probably don't need to do any special tests for it. I would probably really consider it if I was doing anything like video, audio, or other such stuff where available codecs matter and might differ between browsers.
This is me!