jquery-archive / jquery-mobile

jQuery Mobile Framework
https://jquerymobile.com
Other
9.7k stars 2.41k forks source link

.live() not working in mobile safari nor in phonegap application #1852

Closed emile818 closed 12 years ago

emile818 commented 12 years ago

I tried using .live within a phonegap application and it turned out not to be working. I tried .bind() and it is working fine. .live() not working as well in mobile safari, but in normal pc browser.

pascalchristian commented 12 years ago

I second this, seems to be an issue on the latest build. Works well on chrome but not on iOS (tested on iPad 4.3.3) and android browser (tested on Galaxy tab, Froyo 2.2). My latest backup that works fine is dated 6/17.

pascalchristian commented 12 years ago

edit: after further testing, I can't actually pinpoint the issue. Some of my script under .live() seems to work and some do not. Changing .live() to .bind() does not seem to fix the issue completely. Again, under chrome everything seems fine.

scottjehl commented 12 years ago

Thanks. Live() is a jQuery core method, not jQuery Mobile. Are you finding that jQuery Mobile is interfering with its functionality, or should this bug be moved to the jQuery bug tracker?

pascalchristian commented 12 years ago

Hm, good point. It seems that only live("pagebeforeshow") and live("pageshow") seems to be affected. It's really hard to debug though since it performs well on desktop, and only buggy on mobile :(

emile818 commented 12 years ago

pascalchristian: which version is working? i can rollback jquery since .live() is extremely important.

pascalchristian commented 12 years ago

The latest version which work for me are 16/17 June nightlies. If you can provide me with the compiled jquery.mobile.min.js dated around that I will be very happy to test it out :)

emile818 commented 12 years ago

this combination is not working. The issue is from jq 1.5.2 i believe

toddparker commented 12 years ago

We're only going to be supporting jQuery core 1.6.1+ when we release 1.0 so I'm closing this issue as it seems tied to an older version of jQuery core.