Bug 5537 - Support <video> HTML5 tag
: Support <video> HTML5 tag
Product: Browser
MicroB engine
: 5.0/(1.2009.41-10)
: All Linux
: Low enhancement (vote)
: ---
Assigned To: unassigned
: microb-bugs
: http://openvideo.dailymotion.com/
  Show dependency tree
Reported: 2009-10-17 12:55 UTC by Tomasz Dominikowski
Modified: 2010-02-09 16:57 UTC (History)
3 users (show)

See Also:



You need to log in before you can comment on or make changes to this bug.

Description Tomasz Dominikowski (reporter) 2009-10-17 12:55:33 UTC
(Control Panel > General > About product)



Go to any website demo-ing the HTML5 video tag and try playing the video.


Videos should play without any problems, this is Firefox 3.6 engine, right?


Only the video controls get loaded, but the video itself does not. Which means
that probably the codecs are missing. The preferred codec is Theora, which is
patent-free. This codec should get added and hooked up to the browser engine.
Otherwise the web experience is incomplete.




None that would interfere.


User-Agent:       Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:
Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14
Comment 1 Andre Klapper maemo.org 2009-10-17 16:16:32 UTC
"Popular"? Cough. Not yet I'd say, though I cross my fingers. :-P

Can you please provide an example website URL?
(Also for future reference, please.)

Is ogg-support from Extras-Testing installed?
Comment 2 Tomasz Dominikowski (reporter) 2009-10-17 18:49:35 UTC
I just installed ogg-support, but it obviously makes no difference. ogg-support
provides the Vorbis audio codec, not the Theora video codec.

As far as examples go, just visit http://openvideo.dailymotion.com and try
playing a video. The site will congratulate you for using a modern browser and
proceed to load the HTML5 content. The controls will load, but no movie will
ever load.
Comment 3 timeless 2009-10-17 19:26:04 UTC
So. support for audio/video requires support for one of:


in the browser

during development, certain members of the corporation were unwilling to allow
the latter.

support for the former required a gstreamer pipe to be built. among the many
things i did during the cycle was give feedback to someone at mozilla working
on such a pipe.

announcing support for video/audio or certain codecs is typically left to
marketing since they like thunder and bling, so if there is news on those
fronts, i think i'll leave it to them to announce. believe me when i say that
the browser team is looking forward to a day when we can watch videos in the
browser without flash.

i'm not really sure what to do with this bug.

Also, if daily motion isn't correctly handling browsers that decide not to
handle its content types or its media formats, then i respectfully request that
you file a bug against them.
Comment 4 Tomasz Dominikowski (reporter) 2009-10-17 19:41:08 UTC
I think DailyMotion correctly detects the Gecko engine as fully capable of
delivering OpenVideo content, it's just the codec that is missing.

This is a weird situation. Why would anyone deny users functionality that is
clearly the future of the Web and that is royalty and patent-free? From my
perspective it would just be an added bonus. The Theora codec can be ripped out
of the Media Player for all I care, if this is the real problem, which is
"manifesting" support for open standards in direct competition to licensed
codecs on the device. I guess we still have ways to go before Nokia is truly
open. :(
Comment 5 timeless 2009-10-17 19:50:07 UTC
I'm pretty sure you're wrong.

javascript:document.createElement("video") in my MicroB says:
[object HTMLUnknownElement]

the same javascript in firefox 3.5.3 on my mbp says:
[object HTMLVideoElement]

Which means that if they claim the browser is good enough to support Video but
doesn't support some codec, they're sniffing the wrong glue.

I've given you your answer, please don't pollute this bug with advocacy that
asks political questions.

Actually, since you've done that, i'm going to simplify my life:


The bug should have had this summary:
Add support for the html5 <video> tag

The browser will get support for the video tag when there's support that
management is willing to ship, not before. Advocacy in a technical bug tracker
will not help.

Such advocacy will piss off the engineers trying to work in the bug tracker and
make it less attractive to other engineers. This should never be your goal.

From my perspective, including it would have been great if it worked right, was
thoroughly tested and meant we could have extra features provided and fewer
people whining. However, engineering perspectives don't always win.
Comment 6 Andre Klapper maemo.org 2009-10-17 21:21:53 UTC
So we have two issues here.

The first is that Theora is not available. The situation is the same as with
OGG. Please see bug 176 comment 125.

But even if Theora was available the browser in Fremantle would still not
support the <video> tag, as timeless wrote here already.

So there is definitely a bug with the Dailymotion website too as it implies
that the Fremantle Browser supports this, which is not true.

I would not close this as INVALID as this is a valid request, hence reopening.

It *might* end up as a WONTFIX, however as this is getting into politics
instead of technical issues (again: as timeless already said) I'm going to CC
Quim here & prefer to currently keep this ticket open, with enhancement status.
Comment 7 Tomasz Dominikowski (reporter) 2009-10-17 21:41:28 UTC
Sorry, didn't mean to piss anyone off. I just want this to work, that's all.
I'll refrain from politics.
Comment 8 Quim Gil nokia 2009-10-20 14:46:52 UTC
Resolving as BRAINSTORM ("INVALID" is the closer resolution available, sorry).
Please go to http://maemo.org/community/brainstorm/ and file a proposal there
explaining what is the problem and what is the solution you propose.

HTML 5 is still still not stable according to the W3C so it makes sense that we
don't jump to it for a commercial product like the N900. I believe things will
come just as they get standardized.

Theora yes, is basically the same thing as with Vorbis - only that the codec
itself is less popular and the performance less optimal. There is Bug 176 open
so there is really no need to open a Brainstorm idea for this. We are still
working internally.
Comment 9 Stephen Gadsby maemo.org 2010-02-09 16:55:48 UTC
Sorry for the noise. I attempted to change the resolution of this issue from
INVALID to MOVED in keeping with other enhancement request that were bumped
over to Brainstorm. However, it doesn't appear I'm able to do that.
Comment 10 Andre Klapper maemo.org 2010-02-09 16:57:08 UTC
Ah, let me do that :)
Comment 11 Andre Klapper maemo.org 2010-02-09 16:57:20 UTC
The scope of bugs.maemo.org are bugs and only very specific and no-brainer
enhancement requests. This report contains a feature request that is too
generic for bugs.maemo.org. Please post this problem and propose your
solution in Maemo Brainstorm instead:

More information: http://wiki.maemo.org/Maemo_brainstorm