I had worked around this problem by removing the href's from my anchors and using click handlers to change the pages.
However, since taking the 4.1 drop the URL dropdown problem has returned and it seems worse. Some pages the URL bar drops down and even stays there.
Does anyone know what causes this or what I can do to work around it? I experimented with replacing the anchors with <button> and this seems to work OK but I can't do this for the back button. It leaves ugly spacing in the header.
I just migrated from alpha 3. I thought that 4.0 and up had support for desktop browsers. It still works fine in Safari and Chrome. Is there something special I need to be aware of to get those to work?
It seems fail at the main page where I programatically change to a hashed page. Any ideas?
when dynamically generating a list, if i use <a href="#"...> on my list items, click on them drops down the URL bar. If I remove the href="#" clicking on them does NOT drop down the URL bar. So this fixes my problem for lists as well.
seems to me that the capability exists to stop the dropdown and it should be implemented in jquerymobile framework.
So, I am trying to respond to an event where the user wants to clear his inputs. If he has typed more than the number of rows, the textarea increases as expected. However, when he hits clear or I need to manually remove all the input (such as when a save occurs), the textarea does not go back to original size.
to be more specific, i find that when navigating through the app sometimes the user may take certain paths which cause the back button to behave strangely. i guess really it is behaving by popping things off its stack, but it seems to me it would be far simpler just to have the back button as a static link always directing the user back to the same place(s).
Am i missing a fundamental point here?
edit: i thought about this a little more. it seems to me that the fundamental difference between a web-site and an app is that in an app you know exactly where you want to go, whereas as when you are navigating through a site, you may know that on some page there was something you need to see again so you mash the back button until you find it.
if you do this on an app, it could take you through choice and option menus you don't want repeated.
i think the solution i am leaning towards is just to override the click handler for the back buttons and point them always to the same page (assuming there was only one path to the page).
hope this makes more sense, and maybe this can be accomplished via manipulation of the second 'false' flag in changeMobile, but that doesn't seem to work properly.
I just grabbed the latest mobilized version of the ui-datepicker off github. the sample works fine.
however, when i load it via a multi-page, the calendar repeats itself three times. when i load it is a separate page (/ui-datepicker/mypicker.html), the calendar renders properly (although the date isn't filled in).
Note that login.html is a multi-page (hence using rel="external")