Hacker News new | ask | show | jobs
by crush-n-spread 3148 days ago
Most everything with CSS Grid is broken on Edge 15, which is what most Edge users are running. Thus Grid is not something you should be putting in production.

https://caniuse.com/#feat=css-grid

4 comments

The same site says virtually nobody, aprox 2-3% is using edge.

You either have to go all the way back to supporting IE11 and ignore everything not supported by 2013 microsoft to capture another shrinking single digit percentage of possible users until they progressively die of old age or ignore Microsoft stuff.

Alternatively start providing a slightly degraded interface with fewer features and a banner. Our website works best with a modern browser with links to up to date edge, firefox, and chrome at top of page. Preferably with a notice regarding dropping support for internet exploder sometime next year.

It also doesn't work in the Firefox fork I use. But that's probably an even smaller market share.

I noticed this when Mozilla recently resigned their add-ons site and starting using CSS Grid support sniffing to determine weather to show the real site or the gimped mobile site. As it is all browsers without CSS Grid are forced to use the mobile site.

It's super annoying.

The new nightly is a huge improvement, maybe you should try it.
> The same site says virtually nobody, aprox 2-3% is using edge.

What? Do you know how many people that is?

Its a lot of people but how many of them are your customers? How much additional developer time are you going to spend to support them. Are you building a less interesting experience for 98% of your customers in order to support the 2%?

For one party maybe the actual user percentage is 0.2% maybe for another its 20%.

The trade offs are going to differ.

Unless, of course, your production site purposefully does not support Edge (or IE) as a matter of policy. Fortunately that applies to me.
You're making the error of assuming that all web applications in production have the same user base and constraints as yours. For example, I work on an application that is a companion app to some larger domain applications that themselves only work on newer versions of Chrome and Firefox. I defacto don't have to support IE, as none of my users can use it. Additionally if you make a developer focused tool like bug reporting, APM, or log aggregation, you can probably ignore IE, if you don't target Windows devs.
I've run it in production, with the ms-prefixed workarounds. It actually wasn't too bad to get that going, but I look forward to not needing that.