search

google / material-design-lite

Material Design Components in HTML/CSS/JS
https://getmdl.io
Apache License 2.0
32.27k stars 5.04k forks source link

Analyze autoprefixer targets #2697

Open Garbee opened 8 years ago

Garbee commented 8 years ago

Our autoprefixer browser targets currently sits like this:

[
  'ie >= 10',
  'ie_mob >= 10',
  'ff >= 30',
  'chrome >= 34',
  'safari >= 7',
  'opera >= 23',
  'ios >= 7',
  'android >= 4.4',
  'bb >= 10'
];

We should review these numbers based on our target support and some existing usage analytics. For example, Chrome 34 is quite dated (up to like 49 in dev channel.) Seems safe focusing only Chrome-wise to update this to around 45 (considering current stable is 47, give a little headroom.)

Our Android support is also targeting 4.4+. Should we look into handling android issues that go back a little further (as we already have with the menu icon being problematic in older webviews)? If so, that should be pushed back or we need to make it clear which Android webview versions we support internally.

Firefox is currently at version 43. 38 is the current ESR version with 45 being the next up. At the time the update of browsers happens, we should use the latest ESR version for a support target. This way we are targeting the slowest upgrade path of FF while still staying fresh enough to hopefully not bloat the output with uneeded prefixes.

surma commented 8 years ago

:+1: should def. be reviewed for v2, considering we will most likely drop IE10 etc.

Garbee commented 8 years ago

ooh, even dropping 10 too? I thought we were just dropping 9 to be able to use full flexbox.

surma commented 8 years ago

6 days until Microsoft drops IE10 support. Let’s move forward!

listepo commented 8 years ago

:+1:

Garbee commented 8 years ago

@listepo We ask that comments be constructive towards getting things done. +1, or "we need this", etc. type of comments only create noise for the project. If you want updates, there is a subscribe button in the right column you can click to get updates only on specific issues of interest.

Garbee commented 8 years ago

In working on getting PostCSS working (an all-day affair) I needed to put the browser stuff elsewhere so it could handle it. I came up with these quick defaults.

We should have a discussion on IE10. I was thinking about that today and I'm not seeing any compelling reason to drop it other than "one less thing to deal with." But, more on that later, right now I'm too tired.