marekdedic
remove transition test which was only necessary for ie8, which is no …
…longer supported
Given that readme indicates that ie8 is no longer supported, i got rid of the transition test. It's not needed for ie versions > 8 , right?
According to https://caniuse.com/#feat=css-transitions IE9 doesnt support it either. Then again, should we really still support that old stuff? Maybe get rid of IE below 11 for a v1 ? what are your thoughts @paxperscientiam @GenaBitu ?
Ok, let's talk browser support:
I would really like to see some automated browser support testing as part of the lints. I am familiar with eslint-plugin-compat (for eslint) and stylelint-no-unsupported-browser-features (for stylelint) - there should be something similar to that for csslint as well. Will try to add a PR for this if we reach some conclusion.
I tend to support even IE8, I generally use the lints as a guideline and use cover 99%, not < 0.1% as the preferred coverage setting.
I think this discussion is largely subjective (i. e. you see a lot of arguments about this...). I agree that IE8 should die, but the fact is that some people still use it and I want my sites to work for as many people as possible. Also, bear in mind that in some countries, the browser usage chart looks vastly different.
To sum it up (as if this comment wasn't long enough...): 1) We should talk browser coverage, not individual browsers. 2) We should have automatic lints. 3) I support the aforementioned coverage "query".
These days, projects include pre-built files under "dist" that are meant to be ready for consumption.* Since this repo includes source files, any developer is free to choose to ingest them into their own build process.
In short, if your preferred compatibility profile for your dist files is insufficient for some dev, they are free to use the source files.
*To put it another way, the "dist" files are a mere convenience and not guaranteed to meet every developer's needs.
Does that help?
EDIT: My underlying motivation was to see that CSS transition stuff moved out of the JS; however, the fact that it is a function of developer input makes that impossible. Then, I thought about using jQuery, but jQuery animate is limited in that it doesn't handle browser compatibility issues like jQuery ui. OK, i'm getting off topic.
Another approach would be to go "fuck ie8-9" with the dist files, but maintain support in the source.