I've run a variety of non-Chrome browsers (currently Brave) as my default for most personal usage. But with all of them it seems like I run in to incompatibilities that cause me to fire up Chrome as a workaround. I use 5 SAAS applications to run my business and I run them all from Chrome because at one point or another I ran in to some kind of showstopper and it just wasn't practical to constantly switch to Chrome to unblock.
The issues are often weird and not obvious. Last weekend I stayed at a Hampton Inn and their Wifi authentication page kept refusing to accept my last name and room number. I called the front desk which ended up being a waste of time (I was hoping maybe there was a mix up in the data). I finally ended up hot spotting. Then the next day it occurred to me that maybe it was a browser issue. Sure enough, I was able to reproduce the problem in Brave, then copied to the url to Chrome and it worked fine.
Bottomline, these issues seem like a big impediment to a mainstream migration away from Chrome.
It likely involved us blocking a 3rd party script that the hotel embedded against its 1st party interests. If you click on the lion-icon in right end of address bar and lower shields you should be able to match Chrome's behavior, if such a 3rd party script block caused the symptom.
This is why it is very important that we complain when things don't work. It's the only way to slow non-Chrome browsers from becoming more and more marginalized. Hopefully we can turn the tide and eventually make using alternative browsers a pleasant experience for the non-technical users.
The issues are often weird and not obvious. Last weekend I stayed at a Hampton Inn and their Wifi authentication page kept refusing to accept my last name and room number. I called the front desk which ended up being a waste of time (I was hoping maybe there was a mix up in the data). I finally ended up hot spotting. Then the next day it occurred to me that maybe it was a browser issue. Sure enough, I was able to reproduce the problem in Brave, then copied to the url to Chrome and it worked fine.
Bottomline, these issues seem like a big impediment to a mainstream migration away from Chrome.