- cross-posted to:
- lealternative@feddit.it
- cross-posted to:
- lealternative@feddit.it
EDIT: Apologies. Updated with a link to what gorhill REALLY said:
Manifest v2 uBO will not be automatically replaced by Manifest v3 uBOL[ight]. uBOL is too different from uBO for it to silently replace uBO – you will have to explicitly make a choice as to which extension should replace uBO according to your own prerogatives.
Ultimately whether uBOL is an acceptable alternative to uBO is up to you, it’s not a choice that will be made for you.
Will development of uBO continue? Yes, there are other browsers which are not deprecating Manifest v2, e.g. Firefox.
Not necessarily. The problem is often that chrome JavaScript implementation can be ever so slightly different from FFs. Or just that the web devs wrote fragile code that is barely working on chrome and doesn’t work on other browsers, where they failed to test.
Worth keeping around at least
Out of principle, I refuse to pretend I am not browsing with Firefox. 🦊❤️✊ Let website statistics show! And I will boycott sites that break due to not testing on multiple browsers!
I thought like that until youtube started intentionally slowing firefox identifying clients. As soon as I changed my user-agent to match chrome’s the speed was back to normal.
Lol I blocked all but essential JS on YouTube with NoScript and never faced any problems at all. Videos load just fine without extra penalties.
That works until it’s your bank or credit card website. I cannot use Capital One’s (CC) “pay bill” any longer.
Change banks
Luckily it hasn’t come to that for me yet. But I have reported issues with my bank’s website to them, and it had been fixed.
Weird.
Super annoying to have to fire up chrome (brave) to pay my CC bill
“Please use Google Chrome or Microsoft Edge to have a safe banking experience”
Yeah, fck you!
Have you tried either an aagent switcher, or trying with extensions disabled? Just curious if either solves it.
I haven’t because I’m always trying to do something, then I do think to troubleshoot after