I have used the jQueryUI spinner example to show that adding 'type="number"' causes a double set of up/down arrows to be displayed in Safari 6.0.2 and Chrome running under Mac OSX 10.7.5. There seems to be not only the jQueryUI set of arrows but also a native set of arrows. No problem with Firefox.
In my app there is a page called pageStartList. It has a button labelled Options, and when you press that button it brings up a dialog, called dlgStartListOptions. In this dialog there is a Select menu, called slo_SelectClub.
What I would like to happen is that immediately a change is made to the Select menu (slo_SelectClub) that the dialog (dlgStartListOptions) will immediately close.
What I tried was this:
$("#dlgStartListOptions #slo_SelectClub").live('change', function() { var sClub = $('#slo_SelectClub').val(); $('#dlgStartListOptions').dialog('close'); });
It doesn't work. I think the reason is that JQM has created another dialog, for the popup Select menu, and that dialog is still being displayed when the "change" event handler is called - so perhaps at that point my dialog('close') call will screw things up.
One hint that I'm on the right track is that the URL when dlgStartListOptions is first displayed is: .../myo/#pageStartList&ui-state=dialog
but the URL when the "change" event handler is called is: .../myo/#pageStartList&ui-state=dialog&ui-state=dialog
Note the second "&ui-state=dialog".
Does anyone have any suggestions for me? Is there a better event I could handle? Or is there a better way to wait for the select menu to close before calling my dialog.close Or should I take a completely different approach ;-)
Is there some way to determine if the XML returned via a $.ajax() call is well formed?
My experience is that if badly formed XML is returned (eg: a missing ">") then the return value is "success". However I notice that data.childNodes[1].textContent contains a very specific error message that points to the line which has the syntax problem.
Is there any (documented) way to know if the "success"-ful call to $.ajax() actually returned a poorly formed XML file?
I'm developing a jQM app that provides event schedule info (similar to the jQuery conference app that helped us get to the proper room to hear the speaker we wanted to listen to).
So, I deploy my prototype and the first request I get is for some way to print the information! Nice - isn't the whole idea not to have to do that?? But it is a legitimate request - at least until I can provide the information while the mobile device is not connected to the web.
My question: does anyone have advice about printing from jQM? In particular I can see that printing from a desktop browser makes sense, but I don't see that it makes sense to print from an iPhone (how would you do that??). So do I need some kind of way to detect if there is a printer around?
Looking at the first two examples on that demo page:
1. "Select Shipping Method" - I can select a shipping method from the small pop-up list (eg: "Express: next day") and then press the page's "Back" button. No problem
2. "Your State" - this is a problem. I can select a state from the long pop-list (which jQueryMobile displays on a new page because it is too long). Everything looks okay, but when I press the demo page's "Back" button - well, the screen goes white.
I've seen this behavior in both Firefox 3.6.13 under OSX 10.6.6, and also Safari 5.0.3
1. I have two lists that I am trying to format. The first is on a static page and this works great. The second however is on a dynamically created page. This second one does not work - the list appears but with none of the formatting working (eg: no list-divider formatting). I suspect there is something I need to do to the page content after I dynamically create it, but before it is displayed. Could someone offer advice?
2. Any idea when the next alpha will be released? Curious about any "rough plans"