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

last 3 ChromeAndroid versions gives only last version of Chrome Android not last 3 #156

Closed
jitendravyas opened this issue Jul 14, 2017 · 6 comments

Comments

@jitendravyas
Copy link

jitendravyas commented Jul 14, 2017

http://browserl.ist/?q=last+3+ChromeAndroid+versions

@ai
Copy link
Member

ai commented Jul 14, 2017

Yeap, it is confusing. But this is how Can I Use database works — we can’t change it.

Can I Use contains only data about latest Chrome Android version.

But I have good things:

  1. There is no sense to select last 3 versions of Chrome Android, because anyway, Autoprefixer will use only latest version too. Autoprefixer and all other tools use Can I Use database. And this database contains data only about latest Chrome Android. So even if you select 3 versions, Autoprefixer will add prefixes only for latest.
  2. Chrome Android is equal to desktop Chrome in most of the cases. So if you select last 3 chrome versions, last 1 ChromeAndroid version it will generate prefixes for 3 last Chrome Android version too (because they need same prefixes as desktop Chrome).

@ai ai closed this as completed Jul 14, 2017
@kanongil
Copy link

Why is this not a bug?

http://browserl.ist/?q=ChromeAndroid+%3E%3D+33

When used with babel-preset-env, the generated javascript is unusable on old devices.

@ai
Copy link
Member

ai commented Aug 15, 2017

@kanongil Can I Use data contains only one latest ChromeAndroid. If you know any solution, I am open for suggestions

@Grawl
Copy link

Grawl commented Nov 25, 2022

I have many issues in Sentry logs showing me that there is many clients with Android phones from 2017, so I have to fix them somehow

@rhaksw
Copy link

rhaksw commented Jan 9, 2023

@Grawl did you ever find a solution for clients with old Android phones or outdated versions of Chrome? I'm guessing the answer is no. Some of my site's users mentioned it to me here.

@Grawl
Copy link

Grawl commented Jan 13, 2023

@rhaksw not yet

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

5 participants