Page MenuHomePhabricator

TimedMediaHandler broken in Safari 5
Closed, ResolvedPublic

Description

Multiple Issues on Safari 5.0.3, OS X 10.5 PPC:

  1. Opening http://prototype.wikimedia.org/timedmedia/Main_Page freezes Safari. "Spinning wheel of death appears & disappears every 5 seconds. Switching to other tabs is slow. Tab is closed ca. 7 seconds after pressing the X.
  1. Playback needs long to start: On http://prototype.wikimedia.org/timedmedia/File:File-Arborophila_brunneopectus_pair_feeding_-_Kaeng_Krachan.ogv it takes 10 seconds of the spinning wheel until playback starts.
  1. Playback stops nearly immidiately. When pressing play or seeking to a specific time, the video flashes for half a second and the credit screen is opened.

Version: unspecified
Severity: major

Details

Reference
bz29814

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:36 PM
bzimport set Reference to bz29814.

Java Plugin version: 1.5.0_22 (TMH uses Java for Safari, right?)

mdale wrote:

It would be good to know if your using the quicktime component or java. They both have stability issues but one may be worse than the other and we can target the one that sucks less.

Also we may recommend safari 5 users add the http://code.google.com/p/webm/downloads/list webm component if that ends up better maintained and would not be broken when you issue seek requests.

As a practical concern safari 5 bug are challenging, because I don't have a mac readily accessible to test on.

I think Ogg quicktime component still does progressive download to your seek point, so seeks appear broken. In theory someone could update the quicktime ogg component to use the ogg index if we can hunt down the maintainer. But in practice we are probably better off putting our efforts towards webm component testing and bug reports since it seems to have a little more activity: http://review.webmproject.org/gitweb?p=webmquicktime.git

All videos in TMH will have at least one webm transcode.

(In reply to comment #2)

It would be good to know if your using the quicktime component or java.

It's trying to use cortado, but stops after a split second (the cortdo embed is removed from the DOM as well)

Also we may recommend safari 5 users add the
http://code.google.com/p/webm/downloads/list webm component if that ends up
better maintained and would not be broken when you issue seek requests.

Haven't tried it, but this could be displayed more prominently. (Instead of we recommend firefox, we recommend installing this extension. It's easier to get people to install an extension than to switch their browser)

All videos in TMH will have at least one webm transcode.

And h264 is completely out of the question for you?

mdale wrote:

Yes I believe h.264 is still out of the question. But given the foundations priority to support mobile devices perhaps this can be reconsidered. It would have to be proposed on foundation-l with all the related fan fare.

I think your right that we could better feature the recommendation for WebM component. But I have not had a OSX box around to test its stability and it has not be characterized by Google as outside of 'alpha' stage. So can't have the software recommend it without more information about how it performs.

(In reply to comment #3)

(In reply to comment #2)

It would be good to know if your using the quicktime component or java.

It's trying to use cortado, but stops after a split second (the cortdo embed is
removed from the DOM as well)

I attached a log with the output from Console.app. Apparently Safari doesn't have a java console anymore, it is all spewed to the console logging of Safari app itself.

Also we may recommend safari 5 users add the
http://code.google.com/p/webm/downloads/list webm component if that ends up
better maintained and would not be broken when you issue seek requests.

Haven't tried it, but this could be displayed more prominently. (Instead of we
recommend firefox, we recommend installing this extension. It's easier to get
people to install an extension than to switch their browser)

perian works beautifully btw. Haven't had any issues with webm so far on my mac.

Created attachment 8774
Java messages for cortado playback

attachment Console Messages.log ignored as obsolete

perian works beautifully btw. Haven't had any issues with webm so far on my
mac.

I can vouch for perian as well. It's been around since 2006 and actively maintained, so the whole thing is pretty stable.

Created attachment 8775
Same but for FF

It works in FF, added the JAVA log of that one.

Attached:

Created attachment 8776
safari java cortado console output

Attached:

The reason cortado isn't working on Safari 5, is still the 'origin not allowed' exception it seems.

(In reply to comment #10)

The reason cortado isn't working on Safari 5, is still the 'origin not allowed'
exception it seems.

Hmm, I recently upgraded to Lion and upgraded my Java, and I think this issue might now be solved.... At least the player seems to work... More feedback would be appreciated. including from the older platform versions.

Lion works now, and Snow Leopard works icw "Java for Mac OS X 10.6 Update 5". http://support.apple.com/kb/DL1360"

Perhaps someone else can test Leopard with "Java for Mac OS X 10.5 Upodate 10" http://support.apple.com/kb/HT4592 ?

Is suspect this update finally upgrades the Java plugin to use the new live connect API. As this mozilla bug documents: https://bugzilla.mozilla.org/show_bug.cgi?id=517355, the java plugin on Mac OS X was rather out of date and didn't support the new Java 1.6 api yet. It might be that this problem is now finally solved.

Seeking doesn't work, and it is still slow to load, because, well, loading the JVM simply takes long no matter what, but after that, it's reasonably ok.

mdale wrote:

Note: I just tested safari 6 with webm components and it fails with black video.

I don't know if the webm components for quicktime are maintained?

The only version I could find was from late 2010
http://code.google.com/p/webm/downloads/detail?name=WebM%20Component%20Installer.pkg

When safari users visit the page ( before they have the broken components installed ) they do get the please use an html5 browser msg.

brion claimed this task.

Ok, ogv.js started going live last week -- Safari 6.1 and later are supported, and should work pretty reliably now.

Some older versions of Safari (6.0 and below) unfortunately won't work, but should be pretty rare nowadays. We'll be removing what's left of the old Cortado Java player since it doesn't work anymore.