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

Allow era tags (e.g. e-2) for browser support versions #1761

Open
timkelty opened this issue Aug 13, 2014 · 2 comments
Open

Allow era tags (e.g. e-2) for browser support versions #1761

timkelty opened this issue Aug 13, 2014 · 2 comments

Comments

@timkelty
Copy link

Example for setting to "2 versions back":

$browser-minimum-versions: (
"chrome": "e-2"
);

Spawned from: #1524 (comment)

@d4nyll
Copy link

d4nyll commented Mar 17, 2015

Is the reasoning behind this so that your code will always support the latest 2 versions? If so, it might not work as intended.

From what I understand, the usage data for the *-usage-threshold variables are included with each Compass release, and not updated each time you run compile. Thus, I assume that if this is to be implemented, the version for that browser will also be calculated from the latest version as included with the release, and not the latest version when compile is ran.

Unless Compass can somehow detect the latest version of each browser at the time when compile is ran, I don't see a lot of benefits using (and the effort in implementing) e-2 as opposed to just specifying an explicit version.

@timkelty
Copy link
Author

@d4nyll Yeah, I was suggesting that knowing that it would be tied to the Compass release.

I guess I was assuming (perhaps incorrectly) that if Compass is using caniuse data, they would update the data with frequent releases to Compass.

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