Earlier quoted context omitted.
Well, Chrome and Edge.
Google Chrome and Microsoft Chrome.
agree (as Edge user)
The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
131–140 of 143 posts
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#132Earlier quoted context omitted.
What if Chrome had other bug that you can't work around? Users just would have to update it. It is that simple.
Three things: * Why do you think we can make our users upgrade? We're small, just one of dozens of websites they use per day. And in our line of business, this usually means losing clients (who, BTW, are usually not the end-users). * How would we even be able to tell them they should upgrade if we can't test the version of their browser? * It was Chrome 93 to 95. The bug existed for three months in all versions of Ch…
To be specific, what was the bug and what was your workaround?
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#133User agent sniffing is poor practice anyways. Try to use the feature and react according to the browser's abilities. Analytics and similar can sniff all day though. To push browsers to get rid of UA string, we should all use a UA string extension that uses the same string like "DOG-SHIT". That way it'll start showing up in analytics. And if you're trying to date the "data science" girl, spam the app/website with UA s…
Have more fun with your UA strings! Unclosed quotation marks, XXE strings, Shellshock, they might just earn you a bug bounty. Maybe throw in the EICAR test string as well, getting their shitty antivirus to purge the log files may just help protect your privacy!
Log4j would also be an interesting one there
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#134User agent sniffing is poor practice anyways. Try to use the feature and react according to the browser's abilities. Analytics and similar can sniff all day though. To push browsers to get rid of UA string, we should all use a UA string extension that uses the same string like "DOG-SHIT". That way it'll start showing up in analytics. And if you're trying to date the "data science" girl, spam the app/website with UA s…
So it turned out that Chrome 93-95 had a weird issue with the video element: you couldn't replace the source attribute reliably. Unfortunately, that's something that mattered to us, so I had a hack in place that tested the browser version. It's still there in case someone hasn't updated their browser. Testing the feature was simply not possible. It was either that or just let (a large) part of our users get stuck on…
Yup, the "test for feature availability" attitude doesn't properly account for features which are available yet buggy.
I recently ran into an issue where a media-heavy blog post of mine would sporadically crash iOS Safari. I ended up narrowing it down to my use of ImageBitmap to accelerate rendering images into 2D canvases on the page.
My fix ended up being to modify my ImageBitmap feature check to pretend it wasn't supported on Safari.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#135Earlier quoted context omitted.
That's not possible: it assumes a perfect implementation. As I wrote in another comment: Chrome 93-95 had a weird issue with the video element. You can't test that in JavaScript. The feature exists, it just doesn't work correctly. You sometimes have to work around bugs in certain versions of certain browsers. > Just force the switch to better methods. I always thought software developers should have the needs of user…
What if Chrome had other bug that you can't work around? Users just would have to update it. It is that simple.
Last time I had resort to UA sniffing Firefox had issues with clikable horizontal/vertical lines on SVG. There was no version that supported it properly. So I should just display "Switch to Chrome" banner for Firefox users? Is it that simple?
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#136Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#137[deleted]
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#138Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#139User agent sniffing is poor practice anyways. Try to use the feature and react according to the browser's abilities. Analytics and similar can sniff all day though. To push browsers to get rid of UA string, we should all use a UA string extension that uses the same string like "DOG-SHIT". That way it'll start showing up in analytics. And if you're trying to date the "data science" girl, spam the app/website with UA s…
Feature testing is a lot harder when attempting to work around CSS bugs in cough cough Safari, unless you use weird things like @supports () and then hope it is fixed in a future Safari.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#140User agent sniffing is poor practice anyways. Try to use the feature and react according to the browser's abilities. Analytics and similar can sniff all day though. To push browsers to get rid of UA string, we should all use a UA string extension that uses the same string like "DOG-SHIT". That way it'll start showing up in analytics. And if you're trying to date the "data science" girl, spam the app/website with UA s…
Feature testing is a lot harder when attempting to work around CSS bugs in cough cough Safari, unless you use weird things like @supports ( ) and then hope it is fixed in a future Safari.
_cough cough_ MediaSource. Mobile Safari is now completely the new IE. It's so sad.