-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Prevent flicker transition betweeen months - IOS6/iPhone #178
Comments
noticed this as well! |
The datepicker looks awesome on iPhone, but unfortunately the flickering breaks the feeling of a solid component. Please prioritize. |
please fix the flicker, happens on iPhone 4 (real device not emulator) |
i would be thankful if this would be fixed |
The problem for us isn't just the flicker, when a user changes months, the whole calendar disappears and then reappears again. This only occurs on iPhone4 (and possibly above). |
Yes. It also occurs on iPhone 5. 2013/8/14 nirajk32 notifications@github.com
|
Hey all, I apologize for the slow response on this. I think I know what is causing this. I will try to submit a patch soon. |
That would be great, I give you a beer! |
If someone can verify the commit I just pushed to the edge branch - seems to have resolved the issue for me. @victorantos I’ll take you up on that next time you’re in Toronto ;) |
The flicker is gone for me. On iOS 7 beta 5 with Chrome and Safari and on Android 4.3 with Chrome. There is a litte "dot" left which is seeable right after clicking the change month buttons - not a real issue for me, just to let you know. Btw, If you tweak on the overall speed of the datepicker a give you a case of a german beer of your choice ;) Thx. |
@elmcrest not sure I see the “dot” you’re talking about. The fullscreen is due to the media query breakpoints. Anyone can tweak that (and the speed of the picker) in the |
Great job dude!
There's a short "flicker" when you change current month to another one (reload) in IOS6/iPhone, is there something to avoid it?
Thank you for yor work!
The text was updated successfully, but these errors were encountered: