Heres a fun Firefox fact. Firefox handles audio/media files differently than chrome. Since it has a small market share, it becomes a rather annoying lose-lose: either spend a bunch of time to support Firefox for the ~20 people that will access your site using Firefox, or you don't support Firefox.
It's a shame that laziness is more important than interoperability. Part of the life of frontend or webdev is dealing with compatilibity issues, and it has been that way since forever. If you got into this biz thinking you could do that work and avoid those problems you thought wrong.
Laziness? Don't you mean unpractical and financially unviable? If I support Firefox do I support Edge, Opera, Android Webview, UC Browser? Explain how pragmatic prioritization can constitute as laziness.
