They developed the "privacy sandbox" together.
Yeah that's not true.
They developed the "privacy sandbox" together.
Yeah that's not true.
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.
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?
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?
"Vivaldi is closed source, therefore it's harder for users to investigate", which is clearly an inaccurate statement.
Why is it an inaccurate statement?
What user are you thinking of?
You really felt misled that it was harder to inspect? What makes you think I have the expertise to inspect this? I'm not even a user and I wouldn't know where to start to find the ad blocker within that tarball. Would you?
In any case, I clarified why it was harder to inspect - to me it felt obvious that being closed source made it harder to investigate. The fact that it is also shared source really has no bearing to the general observation, especially since we're talking about a 2GB tarball where I don't even know where to start. And I'm a pretty technical person.
How would a user easily investigate this vs. an open source browser?
Source?