-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Assertion Failed on type="tel" input field #2341
Comments
Can you please post a jsbin or jsfiddle test page so we can reproduce this? This page has a the: link |
Dear Todd, |
Thanks for following up ora726 |
I'm observing the same thing. Changing all the "tel" fields in my app to "text" eliminates the error. jQuery 1.6.3 |
jsFiddle: http://jsfiddle.net/TVxvX/1/ Have the Console open and click the "Submit" button in the Result pane. You'll see several very unhelpful "Assertion Failure" messages logged in console. Next, clear the console, change the input type to "text" and resubmit. No more errors. jQuery is choking on type="tel" somehow. Tested in: |
Re-opening. Thanks for the test page. |
Actually I see this on a page with no JavaScript, just HTML markup on Safari 5.1. When the Web inspector sees an input of type "tel" it chokes. However, this error is not generated in the nightly build of Safari Webkit. I'd say this is a bug in the Web inspector. |
Ok, so we can re-close then? |
I ran my tests and could reproduce the pb only in safari, so it look like rblggs is right, it is in Safari. |
Thanks for following up ora726 |
To not get the assertion failed error, and also get a numeric keyboard on iPad, I found this solution: Zip Code: http://stackoverflow.com/questions/593245/iphone-web-applications-and-specific-input-types |
Have noticed that when using a input of type tel the javascript console return an error "Assertion failed". Only this type of field seem to generate the problem. If the error is expander I get :
(anonymous function) :444
(anonymous function) :638
TheHTML looks like this :
...
...
There is no javascript running on this particular field other than whatever jquery mobile does with it.
I have reproduced the same error in Safari (Mac OSX) and Chrome (Osx).
I use the latest jquery and jquery mobile b2.
The error does not create any problem with jquery mobile or my own code, so it seem to be a minor problem but I though somebody might be interested.
The text was updated successfully, but these errors were encountered: