Mark Panaghiston
unread,Aug 23, 2011, 11:30:48 AM8/23/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jpl...@googlegroups.com
There are still some issues with the iOS browser. It does not like having multiple instances on the page and does sometimes fail. Since all the media is played via QuickTime on mobile safari, it is this player that is getting confused by the JavaScript that sets up the audio. This is probably due to the single media at a time restriction, so each of your instances sets up the media to play. The 1st sets it up and then the 2nd changes it and then the 3rd would be setup to play. Only 1 can play at a time, so there is some bug somewhere it it.
9 times out of 10 though, you do not need more than 1 jPlayer instance on the page. Especially in mobile devices this makes sense, as only 1 media can play at a time. Also all the user gesture requirements on the media help if only 1 instance.
I had believed that this problem was now only affecting the media player demos, where we jump between audio and video media types.
If you want to continue with multiple instances, then I suggest that you use the {preload:"none"} option. Preload is actually ignored by iOS, but inside jPlayer there is a slight difference where the .load() command is issued. This should be removed, but is not possible or all the older HTML5 browsers would fail.
I foresee a situation where we will have to browser sniff for all the browsers that are HTML5 (transitional), but not the current W3C spec.