Hacker News new | ask | show | jobs
by vikingcaffiene 3336 days ago
I love stuff like this and it looks fantastic, but without support for at _least_ IE10 I would be loath to use it. IMHO the value proposition of a CSS framework is that it saves time and looks good without having to think about it. If I have to spend time fighting browser bugs and writing CSS hacks to deal with incompatibilities and/or layout issues, that's the opposite of that. Hopefully the developers will add support for some legacy browsers perhaps as an optional addition similar to how JQuery does it.

Fantastic work so far to the developers that said. I will be keeping an eye on this. Good luck!

3 comments

They say that they support older browsers and, from testing it lately, I haven't seen anything odd in IE 10 and 11, except the way images scale in the card media sections, which isn't really an issue in my eyes.
With automatic windows update there aren't really that many users left who are using IE version lower than 11. Browser stats metrics show that only 0.1% of all users are on IE < version 11.
What really matters are the stats for one's own users but who's stats say <IE11 is less than 0.1%? NetMarketShare reports of global desktop browsers for April [0] says:

IE11 13.62% IE8 2.25% IE9 1.32% IE10 1.06%

Wikimedia global all-device browsing for April says:

IE11 4.8% IE7 3.0% IE9 0.43% IE6 0.38% IE8 0.25% IE10 0.23% IE4 0.22% (! I don't know what this is about, maybe an old mobile version?)

[0] https://www.netmarketshare.com/browser-market-share.aspx?qpr...

[1] https://analytics.wikimedia.org/dashboards/browsers/#all-sit...

Yes exactly, I know I'm late to the discussion but I hate when people state you font have to support a browser because it only has x% market share.

It's all about your own users. I'm doing UX and front-end for a company that deals with a lot of IE8 users... -_-

The ongoing theory is that they are on hacked XP copies since that traffic is coming out of China.

I wish they could somehow learn about Firefox, which is still supported on Windows XP. Then it would basically be just the people with old phones and 6-7+ year-old Macs that would require fallbacks.
That's a very skewed audience though, web developers aren't going to be using a super-outdated browser and Microsoft's browsers have been an unpopular choice of that audience for a very long time.
I must have some bad luck then, because we're still seeing lots of corporate customers whose users are still stuck on IE10.
The developer of mini.css addressed these concerns about IE support in a Hashnode story[0], raising some pretty compelling arguments about why it can't be done, not fully at least.

[0] https://hashnode.com/post/the-legacy-support-conundrum-or-wh...