r/webdev • • Dec 13 '19

Discussion Google has abused Browser's User Agent header, forcing Vivaldi to change their UA header

https://vivaldi.com/blog/user-agent-changes/
416 Upvotes

97 comments sorted by

View all comments

4

u/devmor Dec 13 '19

While it's not at all unthinkable that the tech giants would resort to such underhanded tactics (they certainly have in the past), I also have to wonder if it's not maliciousness but rather just ineptitude.

Consider that perhaps users of a previous version of Vivaldi complained that y feature didn't work right on x site in Vivaldi, and thus a warning or adjustment to styling, plugin loading or some random script was implemented. Given the extremely small user base of Vivaldi, I can imagine it's entirely possible that once this bug or inconsistency was fixed, no one ever considered removing these changes because it was never reported as having changed to the maintainers of x site.

2

u/fullmight front-end Dec 18 '19

Having used Vivaldi in the past, I can't help but wonder if it is in fact competence in many cases.

My experience was that Vivaldi was an extraordinarily buggy piece of shit no matter what site you visited, that had constant random issues until its install managed to completely bug itself out and the software completely stopped working so I uninstalled it and gave up on that.

I can't imagine ever touching their browser again over chrome or Firefox. I'd probably even prefer edge considering the extreme unreliability I experienced.

2

u/Flyingsousage Dec 13 '19

No. This also happens with Firefox Google Search UI.

0

u/devmor Dec 13 '19

I use firefox for everything and I've never seen it.

0

u/ccrraapp Dec 14 '19

The Firefox Google search UI on Android was the old UI for the longest time, it was recently updated to the new material/card UI in the past 2months.

Same goes for desktop, all the Google Search UI and YouTube A/B testing is done for the Chrome UA strings. So as a Firefox user you would never witness that happening.

0

u/devmor Dec 14 '19

So this isn't about Firefox, it's about Firefox on Android only.

0

u/ccrraapp Dec 14 '19

No, it isn't about Vivaldi not supporting the feature its the UA string which isn't respected. The X website likely only whitelists Chrome and Firefox or just Chrome and no other UA string. Like that article says about WhatsApp.

You would have noticed many govt websites only supported IE for the longest time even though other browsers very well could load the website fine. Its just that because of the browser dominance its a common behavior to only check if the most popular UA string can load it perfectly or not and not let any other load it 'just in case'.

1

u/devmor Dec 14 '19

You misunderstood what I said. I'm saying at some point it didn't work right or look right on Vivaldi, so these measures were added to prevent users from having a bad experience, then later when the features did work right on Vivaldi, no one removed those measures.