-
Notifications
You must be signed in to change notification settings - Fork 725
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
Problem with prompt on iOS #163
Comments
Played a bit more with this. If I hit done to hide the keyboard in the input field and then hit the alertify ok button, I get the same locked up behaviour, I don't get the weird extra callbacks though 😕 |
Is this only happening with the The What was the unrelated issue with 0.3? |
Yes from master (I also tried the 0.4.0rc1 tag). The issue in 0.3 was if you use enter to submit from the dialog (or in iOS the go button) it would still treat it as cancelled, so you could only use the OK alertify button. This occurs on the demo page right now. This seems to be ok in 0.4. |
hello |
I'll be looking at why this is happening in I'll look into backporting to |
Fixed with ^. Will be part of |
great!! On Tue, Oct 8, 2013 at 2:27 AM, Fabien Doiron notifications@github.comwrote:
Alex Hoyau |
Available now:
I will be updating the demo page and docs shortly. |
Closing |
Great, it works, thank you! |
I have an outstanding issue since it seems to have issues with iphone fabien-d/alertify.js#163
…he page see fabien-d/alertify.js#163 I also hard code the input to tel until the following is addressed fabien-d/alertify.js#39
I built the latest code (0.3 had an unrelated issue so I can't use that) and am having issues with prompts (iPhone breaks, iPad seems to be ok, Safari/Chrome desktop seems fine).
If I enter a value and either hit go on the iOS keyboard or hit the OK (alertify) dialog button, the keyboard remains visible (even though the dialog and text field are gone) and the body ends up being disabled. I try touching some of my elements my callback ends up being called again.
Hopefully I've described this ok let me know if I'm not making any sense.
The text was updated successfully, but these errors were encountered: