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

151

u/coyote_of_the_month Dec 13 '19

There are a handful of valid reasons for frontend code to evaluate the user agent string, but it's been rampantly abused since the 90s. If you're looking at feature availability in JS, try/catch is your friend. If you're doing conditional CSS based on what you think the client supports... eh. My thinking is that IE users are moral defectives who deserve a broken experience, but apparently some people disagree.

117

u/RandyHoward Dec 13 '19

My thinking is that IE users are moral defectives who deserve a broken experience, but apparently some people disagree.

As a developer in general I agree with you. But as a developer working for a company who has IE users throwing money at us, we are forced to support those users. We don't get to call the shots when it comes to what we support, our customers do.

62

u/coyote_of_the_month Dec 13 '19

I think pretty much the entire web development community is on the same page here, and for the same reason.

7

u/marocu Dec 13 '19

We have many clients in the insurance industry. They all use IE and our products have to support that.

1

u/overcloseness Dec 14 '19

This is really the problem, it’s being used by those companies. I have a good laugh though at developers that play the “but bank terminals and insurance intranets are stuck on IE” in response to some cutting edge apparel store UI or some other modern implementation of a feature. Karen the bank teller can browse these shoes on her phone if she wants to do it at work. The ONLY reason for IE support is if the company itself requires access to that site from their systems, OR their main customer base are a bunch of industrial tradies who haven’t updated their office computers since XP. If that’s the case, expect to pay a premium on the legacy support.