Probably not, unless you're a really big outfit with a vast user base. But you should test on at least a recent Chrome version and a recent Firefox version, and probably Safari.
And unless your product is irrelevant to mobile users, on both iOS (Safari) and Android (Chrome, Firefox), with both phone and tablet form factors.
https://gs.statcounter.com/browser-market-share at ~3% of overall share / 7% desktop-only share it's hard to justify putting extra effort.
Yes, this is something I've experienced directly from end-user perspective as well as debugging/user-analytics perspective.
grrr
(Test IE11 as well, by all means, if it's relevant to your users; but it's much less relevant to the future of the web.)
Every time they bump into something they dislike about Chrome, they’ll remember who is forcing them to use it. When an alternative comes along and works in their browser of choice, they’ll switch and advocate for it.
We don't know how the situation will look like in the near future. If a large enough portion of the users switch to a different browser, it quickly becomes an issue.
It is in my opinion part of what companies should include in their risk assessments. Looking at the general trends, I would not be surprised if at least EU governments and institutions will ban Chrome due to privacy and data security. That will probably lead to others switching as well.
Ideally, you'd have reliable usage numbers by browser and platform, as well as a threshold of usage that demands testing. Maybe that's 1%, 5%, 10%, 20%? Aggregate up, so if FF desktop doesn't hit the numbers, maybe FF in general does, or maybe 'other browsers' does. Or maybe commit to testing the top N platforms over 1% usage.
Lower on the usage scale doesn't need to be pixel perfect or pretty at all, IMHO, but major site features should still work.
(Disclosure: I am still very much a Firefox user, so this might be projection.)
2. Unless you're running a very low traffic site, it's not like 3% of users don't matter. 3% may mean millions of users.