> I only tested it on Chrome mobile

Why? Wouldn't it make more sense to test on FF? If something works on FF, it's probably going to work on other browsers.

OTOH, if something works on chrome, there's a small probability of it working on other browsers.

I would generally say it is a big probability either way.

> I would generally say it is a big probability either way.

I practice, though, I've never found that to be the case - almost no developer wants to use that tiny set of features only available on FF.

In practice, what I've found is exactly what this thread is complaining about: every developer assumes that those large set of features only found in chrome is found everywhere.

IME, if something runs in FF, it also runs in Chrome, while if something runs in Chrome it sometimes has problems on FF.

Says a lot about the state of web dev in 2023. "Works on Chrome" is good enough for the majority of devs.