Removing Google's binary blobs is mitigating one issue, but replacing it with an entire binary blog from an anonymous github user might be introducing new ones. It's just one of several useful features that make things far easier but lacks full/partial/any support in IE. Either creators design the site to entirely compensate for IE and loose that flexibility (pun not intended), find some Javascript polyfill that actually works/fixes such bugs, or just present some message to users for unsupported browsers (not that it needs to necessarily block the page though). The majority of its bugs, or just plain missing features are found in IE10-11 (and absent completely in earlier versions).
It was made to simplify the creation of page layouts and content flow and includes various features that were sought-after for a long-time that require hacky or more complex solutions otherwise. Microsoft has abandoned feature updates to IE, and sadly only made Edge available to W10 users.įlexbox in CSS is one example. I agree that targeting of Edge browsers is ridiculous since it's keep current, on the other hand for IE and if the site is non-commercial/personal (commercial sites should really try to be compatible on as many browsers as they can) I don't really blame them if they're wanting to use modern web standards. Stop messing around with fancy CSS and JS, spend the time developing a simple site that almost naturally works in IE too. > IMHO, those are "features" which no one really cares about. Guess I must be hallucinating, then? Well, jokes on them 'cause if they hire people who break their website so that I can't check the opening hours, guess where I'll be shopping? Not at their store, that's for sure. I wrote an e-mail to report the issue to the people in charge of the site, and you know what they tell me? Oh, "we forwarded your message to our web developers but they said that this doesn't happen". Talk about messing up with browser detection. These guys took it one step further and had their mobile website decide that I was in fact not on mobile, and then they proceeded to throw me into a redirect loop between the desktop and mobile site. That's not the stupid part, though (just annoying). I visited their website and was, like in a lot of cases where they assume ARMv7 means I must be using a mobile device, redirected to the mobile site.
At the time, I was running Linux on a desktop computer which had an ARMv7 processor. The dumbest user agent based browser detection mechanism I ever encountered was one that a major grocery store chain had in place on their website.