looks like rendering adblockers extensions obsolete with manifest-v3 was not enough so now they try to implement DRM into the browser giving the ability to any website to refuse traffic to you if you don't run a complaint browser ( cough...firefox )
here is an article in hacker news since i'm sure they can explain this to you better than i.
and also some github docs
On the consumer front, almost everything has a web interface layer over the grotesque monster that actually runs the services.
For any business accounts, banks are an entirely different monster. If you've only ever used consumer services, you'll never know the disgusting mess underneath it all. Banks have only done this much for consumers because if they didn't, they would have either lost, or never attracted any of the modern generations to their services, namely millennials, and all those who came after.
The older generation for the large part, is happy to continue using IE, and walking into a bank to do whatever they need to.... But starting with millennials, having browser agnostic web based services to do simple things like bill payments, account to account transfers, balances and transaction records, and most don't need much more than that.
One of the more recent, and possibly most egregious examples was a cheque scanner for a business, which was a USB attachment to a client's workstation for bringing in payments in bulk, rapidly. Think about it like the mobile cheque deposit in your favorite banks app, but on steroids. The bank provided the cheque scanner, and a business login page for the service. The way it operated, from what I could see, is that it required special drivers from the bank for the device, and a series of custom ActiveX plugins, which, as expected, only work with IE. The entire process was essentially to take a high resolution scan of the cheque, and dump the image into the website (I presume, securely), to submit the payment to the bank. This process would be complete in a matter of seconds when it's running correctly. From what I saw from what the bank technician did, remotely, was to load the site in edge, force it to display in an IE tab, then adjust the drivers and signing of ActiveX control to validate and submit the scans.
The mobile deposit does the same but much slower, potentially taking minutes to capture the cheques image and fill in all the details, per cheque. Meanwhile this process could literally process a dozen cheques in the same amount of time. What kills me is that mobile deposit is basically the same thing and they have the structure for it already. It should be relatively trivial to adapt the process to use the cheque scanner to submit the images of the cheque, compared to basically having to registry hack each client computer to work with the antiquated system instead; but they do it anyways.
I was asking for a list of Banks, not multiple paragraphs I've no interest in reading.
All of them.
USAA doesn't not require that I use only Chrome.
You should have read what I said before, it doesn't require you to. Consumer clients are generally immune to the problem. Not all of their customers are.
I can't help you if you choose to ignore what I say, and rely solely on your own anecdotal evidence.
Good day to you sir.