Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider dropping IE10/11 support? #163

Open
simonsmith opened this issue Feb 19, 2019 · 1 comment
Open

Consider dropping IE10/11 support? #163

simonsmith opened this issue Feb 19, 2019 · 1 comment

Comments

@simonsmith
Copy link
Member

I think we can safely drop IE10 now, we might be able to remove a couple of the awkward hacks in utils-flex and grid. The biggest wins however would be from IE11 and transpiling custom properties. We'd no longer need to use :root or the rather convoluted naming for custom properties.

This is a big win in my opinion.

@mlnmln
Copy link
Contributor

mlnmln commented Mar 1, 2019

@simonsmith I think it is safe to drop IE10 by now. IE11 hovers around 2,5% still, so I'd say we would need to respect that unfortunately.

https://caniuse.com/#search=custom%20prop

Anecdotical: We recently (2019) had a project that had 37% IE11 users (local university).

Maybe we could think of creating a "modern" build, similar of how libraries like Vue.js are doing it nowadays, but for CSS?
https://cli.vuejs.org/guide/browser-compatibility.html#modern-mode

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants