I am having trouble getting the HTML5 video action to work with Firefox 3.6.2. I don’t know if it is something I am doing or if it is beyond my control. I’ve noticed that it doesn’t work with the Demo link given with the action description page either. http://users.softpress.com/joe/vid/
The strange thing is that it works when I preview using Firefox, but not when I upload it.
Any ideas.
Thanks in advance for your time.
Strange, it’s not working for me either. I’ll need to take a look after the weekend.
Joe
On 2 Apr 2010, at 13:58, maxstamper wrote:
I am having trouble getting the HTML5 video action to work with Firefox 3.6.2. I don’t know if it is something I am doing or if it is beyond my control. I’ve noticed that it doesn’t work with the Demo link given with the action description page either. http://users.softpress.com/joe/vid/
The strange thing is that it works when I preview using Firefox, but not when I upload it.
Any ideas.
Thanks in advance for your time.
I am having the same problem with the latest version of Firefox. The demo video works, but my .ogv file does not - I just get a grey rectangle with a cross in the middle.
I have added the video/ogg ogv MIME type to the list of valid MIME types on my server.
You need to contact your webhost and get them to add .ogv - video/ogg as a valid MIME type (they should know what you mean).
Joe
On 16 Jun 2010, at 12:53, ralfy wrote:
I am having the same problem with the latest version of Firefox. The demo video works, but my .ogv file does not - I just get a grey rectangle with a cross in the middle.
I have added the video/ogg ogv MIME type to the list of valid MIME types on my server.
Hmm, the file isn’t being served as video still. I can see this by tying in the path to the movie in Firefox, instead of playing the movie directly in the browser the server sends it back as an unknown file type for download.
Compare these two files which are just the movies on their own, so nothing to do with the Action:
Do they see that header when they request the file directly? Firebug
would be a good tool here to see what headers are being sent by the
server when that Ogg file is being requested. Also, if the file-type
was set in the Apache configuration file, then the web server has to
be restarted for that to take effect. If it was done using
an .htaccess file, then the effect is immediate, and there shouldn’t
be any difference between the two in terms of authority.
Walter
On Jun 16, 2010, at 12:12 PM, ralfy wrote:
Joe,
Got this message back from the hosting company:
"I can see the server is setting the correct Content type header
though?