deleted by creator
deleted by creator
The 2FA thing sounds like it’s all on the Dropbox side if you are just entering a code you got from an authenticator app. The Google login issue may be a real issue – did the Google login specifically work on another browser?
There is nothing about MV3 that stops you from improving things.
What about this stuff?
Uhh, that doesn’t seem normal at all. Is this a default config? Any extensions in use?
Probably simpler to just “Forget” the site from the site’s context menu in the history sidebar.
What are you a captcha?
You’re awesome!
Who’s a bot?
deleted by creator
Opera GX has promised to keep MV2 in their code. So I’ll just keep using that until I see something different. The other thing is that Opera GX has built in ad-blocker which is pretty much on par with third parties.
I couldn’t find a source for either of these claims. Can you help me out?
Not trying to be obtuse here, but why are you pruning your history in the first place? Is someone auditing your browsing history? I’m personally not interested in removing my browser history for the most part - and certainly not frequently enough to notice this limitation.
Why not just open private browsing windows if you don’t want your browser remembering those pages? Are you deciding afterwards that you want to forget those pages?
I don’t think I can clear my history without it closing all of my Firefox instances and making me reopen everything.
That’s not true - are you using always private mode?
Firefox can’t fix all the broken sites in the world, but they do investigate issues reported to https://webcompat.com
You can help by reporting sites that don’t work for you.
It basically wasn’t. The original developer allowed a fork on platforms they weren’t interested in, drama ensued and eventually, the Apple thing happened anyway.
uBlock became uBlock Origin once the "origin"al developer took over the project again.
Untrue. Safari never had the real version of uBlock Origin (it was always a port) and it lost many features when Apple moved to a new extensions framework (much like Google). See more: https://github.com/el1t/uBlock-Safari/issues/158
You have to remember that sometimes when that shiny new CSS feature comes out, it is underspecced, with unhandled corner cases – “just do what Chromium does” is not a standard – or is it? Having multiple implementations of a spec prove that it is interoperable - without that, you might have a good spec, or you might have a spec that says “whatever Chrome does is what is expected”. Not sure that is what we want from new CSS (or any) features.