I have an HTML5/JavaScript app built for a car in-dash display unit that I have been asked to port over to run in the browser.
Easy task, made some simple changes and now everything works fine in every desktop browser that I tried in.
Then, came problems. I was asked to specifically make sure it could run on an iPad for demonstration purposes.
THE ISSUE:
The app uses single page navigation, using jQuery.load to load in the necessary page fragments as the user navigates to different ‘screens.’ However, all of the jQuery bindings are centralized in one place so that they are performed on app startup, even though the elements they are binding to may not yet exist in the DOM.
That’s fine using jQuery.live or .on since they allow binding to future DOM elements. At least in desktop browsers.
In Mobile Safari, .live/.on simply do not work for binding to elements that do not yet exist.
I have an example to illustrate this problem here: http://dhines.com/jquery-test/
Notice that all of the ‘SHOULD WORK’ links do work in desktop browsers, but not Mobile Safari!
Looking around the web and SO, the only solution I have found would be to add onclick=”function(){}” to all of my clickable elements. This seems dumb.
The other option I see would be to decentralize my bindings and have them take place on the specific fragments that they apply to, but given the ton of fragments and bindings, this would not be fun.
Looking at my example, can anyone provide me with a better solution? Or perhaps point out whether I’m using .load incorrectly or something?
I can not test this (I have no apple product), but a I have found a discussion on the jquery ticket system:
http://bugs.jquery.com/ticket/5677#comment:7
the trick seems to be to add { cursor : pointer } to the elements I have seen that your example doesn’t define this css property. Give this a try…
Maybe Apple Safari developer thought that an click event doesn’t make sense on an element which doesn’t have curosr:pointer.