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

Don't seem to work on Android 2.3 #17

Open
andreszs opened this issue Jan 2, 2015 · 4 comments
Open

Don't seem to work on Android 2.3 #17

andreszs opened this issue Jan 2, 2015 · 4 comments

Comments

@andreszs
Copy link

andreszs commented Jan 2, 2015

Please, can you fix them to work on Android 2.3 devices? Simply add -webkit attributes and other minor changes to make it work, thanks.

@lukehaas
Copy link
Owner

lukehaas commented Jan 3, 2015

Thanks for your suggestion.
I'm guessing you're referring to the unprefixed box-shadow. I left these out as I think the usage stats for people using very old android browsers is quite low, and including them would add a lot of bloat to the CSS as the spinners are very box-shadow heavy.

@andreszs
Copy link
Author

andreszs commented Jan 3, 2015

Don't worry, rotate is a non-animatable property in Android 2.3, I had to implement it with JS by changing the angle every 50 ms.
To reduce your code, you should remove the non-prefixed attributes from @-webkit-keyframes, and remove the prefixed ones from @keyframes, since those functions apply only to prefixed and non-prefixed attributes respectively.

@ghost
Copy link

ghost commented Aug 12, 2016

Can confirm that the preloader does not work in Android 2.3.

The annoying thing with the Modernizr test and the applied CSS rules with .no-cssanimations is that it will not hide the preloader if you have changed the load-container to position: fixed. In that case it will display the preloader inline, which is a known issue documented here.

Is there a way to completely hide the loader including its container in Android 2.3 in this scenario?

@lukehaas
Copy link
Owner

Android 2.3 is not supported. Regarding your other question, you may find some useful responses if you post it on stackoverflow.

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