Will the video play in firefox but not in the html5 tag?

Question

so we are creating a video site with html5 player (and backup flash for windows).

But what really throws me away is when I look at this file in firefox, which it plays; http: //www.roguefilms.com.local/media/uploads/2010/07/1495/8_lg-poke.mov (stored locally), but when the video does nothing in the html tag. It shows a poster but does not play the video. It doesn’t even show "Sorry - your browser is not supported!"

I know that ff prefers ogg, and we can use the player of the Flash player, but if he can play it like ht64.mov without a player, why can't he? Sounds a little dumb?

If anyone knows anything, it will be great ...

<video controls="controls" id="myVideo" src="/media/uploads/2010/07/1495/8_lg-poke.mov" poster="/media/uploads/2010/07/1495/still.jpg" height="360" width="640"> Sorry - your browser is not supported! </video> 

best dan.

Answer 1

When you simply download the .mov file, your server’s content type provides reasons why Firefox checks to see if any plugins are processing the content. In this case, QuickTime processes it, so it plays.

The video tag does not launch plugins for playing content.

Answer 2

Firefox does not support h264, as you already mentioned, although I am surprised that it plays the video on its own, unless it automatically launches it in Flash Player, which is possible.

To get a "sorry" message, you need to use the source element:

 <video controls="controls" id="myVideo" poster="/media/uploads/2010/07/1495/still.jpg" height="360" width="640"> <source src="/media/uploads/2010/07/1495/8_lg-poke.mov"> Sorry - your browser is not supported! </video> 

I wrote this back in April last year, but it could help: html5laboratory - using the video element .

Answer 3

We had a similar problem with the web server (in our case, Apache), not sending the correct MIME type for the video file, and Firefox first downloaded it completely before starting to play. Is it possible that the player will work if you just waited long enough? You can use Firebug to see that your browser is transmitting something.