Post #2824752

2026-04-14 14:21 UTC

@missingno@social.vivaldi.net @Vivaldi@social.vivaldi.net And when I and others in Vivaldi worked at Opera, we had serious problems with web site compatibility because of it.

Replies (1)

@missingno@social.vivaldi.net 2026-04-14 14:50

@TechieNotNetie@social.vivaldi.net @Vivaldi@social.vivaldi.net I understand that. And I understand the decision to change the default UA string so less techy people won't complain about the browser being broken when it is the faulty website. However, even then Opera was singled out and actively sabotaged by some websites/webservices delivering broken code to it. (So there was also the option to mask it as another browser.) But as you can see, there are still people believing (changing Sec-CH-UA to wave the Vivaldi flag) in an open web. I used to use a user agent switcher extension (doesn't work anymore) and had it set to "Vivaldi/x" without too much trouble. I know Twitter didn't like it, but mostly I didn't experience any issues. Having a temporary debugging option available but no way to set the user agent string to a clean Vivaldi is just weird. It doesn't have to be the default - just give Vivaldi enthuisasts the option, even if it might lead to some broken websites.

Open ##2824753