we have a search box on our form and ideally would like to be able to close the keypad on the iPhone/iPad when the user clicks the search button (rather than the user having to click the done button). Is this possible?
For some reason either JQM or JQ or a combination thereof clears user login information even if they've requested it be remembered - and this ONLY happens on iPhone/iPod/iPads. If you remove the references to JQ/JQM the issue disappears.
my login.aspx page is below. It calls a generic event handler and does a redirect to my Default.aspx page upon successful login.
does anyone have any idea how to get the Android phone to show the numeric keypad when an input is marked as type="number"? The iPhone honours this setting, but the Android browser perhaps hasn't implemented this. Short of this, is there a workaround?
I wish to extend the pageLoading method to allow passing in display text, something like the code listing below. What is the best way of doing this - I do not want to edit the core function, just have my variation called instead.
my application relies heavily on ajax calls to pull data into pages. I have some 10 pages altogether which are mainly placeholders adhering largely to the multipage boiler point template in the JQM documentation. All ajax calls are routed through a single method.
in the browser, there's no noticeable difference in relation to navigating between pages etc.
However, when running the application on an Android phone or an iPhone, I'm experiencing significant issues with JQM version 1.0.a4.1 and I think I noticed issues creeping in in 1.0a3 but fobbed them off thinking it was probably something I was doing or not doing. Certainly, with JQM 1.0a4.1, the user experience is abysmal to a point where people have given up using it, whereas they were very pleased with the experience in JQM 1.0a2.
I've since regressed to JQM 1.0a2 and it's like unclogging a drainpipe. It just flows.
There is no difference in any of the code, just purely swapping JQM/JQ versions.
Am I the only one experiencing this degradation in responsiveness through the iterations of JQM/JQ?
If you run up the following page (updating the reference links as required), you'll notice that when you click on a button, it stays blue. Revert back to version 1.0a3 and the issue is not present. I had problems with 1.0a4 so can't say whether the problem's there as well.
Also, ie9 working much better - but one of the themes (c I think) comes as an unreadable blue.
Is it possible to further filter this if the div contains an element of another class so for instance, divs below with input having class="someOtherClass" would be selected and divs with class="someExcludedClass" would be excluded?
I've been looking at the search input http://jquerymobile.com/demos/1.0a3/#docs/forms/forms-search.html and like the general look and feel. What I'd like to be able to do is provide a search button either to the left or the right of the clear button that pops up as well as the clear button when you have entered text and remove the search icon on the left. I'd like it so you can optionally exclude either of the buttons. So it now looks something like this (note have cut and pasted images from different themes):
I do not want to mess with the jquery mobile core libraries.
Can anyone advise on what is the better way to do this - and point me in the right direction to getting started?
we have Outlook messages converted to html and wish to display them in our application. I have been trying to get this to work trying either just setting the html in a div or using the .Load() method. The only issue has been that the styling in the surrounding pages buttons is impacted. Before loading the button looks as per the nice jquery mobile styling:
afterwards, it looks like this:
any ideas on how to avert this? I have been tempted to use iFrames but they of course come with their own suite of problems.
is there anyway of getting the jQuery Mobile loading dialog to move with the page as the user scrolls down?
Currently, we offer a list of clickable items. If an item in the list is clicked, we show the loading dialog to indicate we are retrieving the details for the clicked item i.e. $.mobile.pageLoading()
This works very well when the list only takes up a single screen. However, in many cases the item the user wishes to open requires them to scroll down the list and the dialog shown by the line above is out of view so the user is confused because nothing seems to be happening.
Is there any way of getting the dialog to reposition so it's always in view?