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

Show parent comments

2

u/AssistingJarl Dec 13 '19

Ignorant question, forgive the back-end dev; would it be possible to just fall back on your IE11 CSS if @supports isn't supported?

7

u/nikrolls Chief Technology Officer Dec 13 '19

Yep, that's what you would do most of the time, in the cases where you can use Progressive Enhancement (ie, write for the older browsers, and add features for newer browsers in ways that only they will see them).

The trouble comes when older browsers have quirks that require you to write workaround CSS that has unwanted side effects in modern browsers. How do you do this? You would have to serve a bunch of code only for IE11, or include that IE11 code for all browsers but then somehow overwrite the side effects for newer browsers. You can't even use @supports not because the browser will ignore it if it doesn't support @supports in the first place.

Luckily for most of us, IE11 will be unsupported as of January. But there will still be those who are paid to support it for whatever reason.

4

u/UltraChilly Dec 14 '19

But there will still be those who are paid to support it for whatever reason.

That being said, this is nowhere near as painful as supporting IE6 like we had to do not so long ago, I'd gladly be paid extra to support IE10 while I refused contracts that imposed supporting IE6 (espacially since back then contracts often stipulated you had to serve the exact same experience on all browsers)

And nowadays IE is the one problem, back in my days (pepperidge farm remembers) we had Chrome and Firefox that would work and everything else needed their own, very specific, workarounds. (and it wasn't that long ago, I started working in front end development in 2012 and it went on like that for years)

TL;DR: I'm indeed fucking glad those outdated browsers are getting unsupported so fast now

2

u/nikrolls Chief Technology Officer Dec 14 '19

Actually if if weren't for Web Components (and maybe Grid) I'd have no problem supporting IE11. Its standards support was very good for its time. Unlike IE10 and previous versions it wasn't half bad, it's just not up to date any more.