Page MenuHomePhabricator

Video files are broken on most mobile browsers
Closed, ResolvedPublic

Description

Author: lmandel

Description:
I'm still seeing the issue playing video files on Firefox on Androied that was reported in bug 30859. Here are steps to reproduce as Naoki commented in https://bugzilla.mozilla.org/show_bug.cgi?id=728486#c9:

  1. go to http://en.m.wikipedia.org/wiki/Red_panda [either on fennec or with Fennec ua on desktop]
  2. select show for "Conservation"
  3. scroll down to "In captivity"
  4. click on the play button

Expected: video to play
Actual: nothing happens.


Version: unspecified
Severity: enhancement

Details

Reference
bz38305

Related Objects

StatusAssignedTask
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
Resolvedhashar
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:05 AM
bzimport set Reference to bz38305.
bzimport added a subscriber: Unknown Object (MLST).
bzimport created this task.Jul 11 2012, 2:57 PM
brion added a comment.Jul 11 2012, 3:06 PM

Hmm, the button is indeed still there:

<div><button onclick="if (typeof(wgOggPlayer) != 'undefined') wgOggPlayer.init(false, {&quot;id&quot;:&quot;ogg_player_3&quot;,&quot;videoUrl&quot;:&quot;upload.wikimedia.org/wikipedia/commons/9/99/Red_Panda_National_Zoo.ogv&quot;,&quot;width&quot;:250,&quot;height&quot;:188,&quot;length&quot;:21,&quot;linkUrl&quot;:&quot;/wiki/File:Red_Panda_National_Zoo.ogv&quot;,&quot;isVideo&quot;:true});" style="width: 250px; text-align: center" title="Play video"><img src="bits.wikimedia.org/static-1.20wmf6/extensions/OggHandler/play.png" width="22" height="22" alt="Play video"></button></div>

Looks like it no longer errors, but it doesn't do anything. It should be getting stripped if we know it won't work.

Same issue on Mac OS X with:

  • Safari 5.1.7 (7534.57.2)
  • Firefox 13.0.1
brion added a comment.Jul 11 2012, 3:19 PM

Yeah it's not browser-dependent, the button's just in our mobile HTML output but doesn't do anything since there's no JS hooked up for it to call.

[And even if it did, Firefox for Android is the only mobile browser that would actually play the Ogg files. ;]

tiffanyb wrote:

A similar problem is happening in Opera Mobile. Opera Mobile uses the device OS' supported codecs; in this case of Android devices, H.264 or MPEG4 will work too.

Using multiple <source type="foo"> or checking whether the format is supported using canPlayType() should fix it.

shwetankd wrote:

Any movement on this? Displaying videos on mobile devices would be a very useful thing, at least on smartphones. The solution posted by tiffabyb should get the job done.

brion added a comment.Sep 17 2012, 5:39 PM

This is still waiting on infrastructure -- we need to actually generate H.264/MP4 transcodes of videos (bug 39869) before we can expose them, and before that we need the transcoding infrastructure working at all.

tiffanyb wrote:

That(In reply to comment #6)

This is still waiting on infrastructure -- we need to actually generate
H.264/MP4 transcodes of videos (bug 39869) before we can expose them, and
before that we need the transcoding infrastructure working at all.

In the meantime, is it possible to hide the video player or otherwise alert the user if the platform doesn't support the codec?

Current state update...

As of updates a few weeks ago, videos actually work now in Firefox. We're outputting <video> with Ogg Theora and WebM <source>s and it understands them. :)

Opera Mobile doesn't seem to play; looks like it doesn't understand WebM on mobile. :(

Safari and IE 10 have the same issue that they don't understand WebM or Ogg, so you get an error or nothing plays.

Will see if we can think of a nice workaround that we can put in place if MP4 isn't going to happen soon... a JS check and hiding the <video> can probably handle it.

What's the latest update here. Is this bug actionable in any way?

brion added a comment.Sep 10 2013, 6:22 PM

The H.264 legal discussion wheels are still moving slowly.

We might split this into two, more actionable bugs:

a) disable <video> and <audio> in mobilefrontend where ogg and webm not supported (probably some JS to detect that it's not working and provide a fallback behavior)

b) enable MP4/H.264 output support on Wikimedia sites

a) bug 58948
b) bug 39869

  • This bug has been marked as a duplicate of bug 58948 ***