Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

HTML5 webm and ogg video not playing after upgrade to version 25

more options

Hi,

I have my video hosted on Amazon s3 and have the mime type set correctly to video/webm and video/ogg. I'm using the HTML 5 video tags which loads a mp4, webm or ogg video.

However after upgrading from Firefox 24 to 25 the video no longer loads, this is a problem specific to Firefox. The console just returns the message "All candidate resources failed to load. Media load paused."

You can find a link to the video here: http://taggled.tv/video/353

Any hints on where I'm going wrong? I've tried changing the mime type on the ogg video to application/ogg as someone recommended this, but still no luck!

Hi, I have my video hosted on Amazon s3 and have the mime type set correctly to video/webm and video/ogg. I'm using the HTML 5 video tags which loads a mp4, webm or ogg video. However after upgrading from Firefox 24 to 25 the video no longer loads, this is a problem specific to Firefox. The console just returns the message "All candidate resources failed to load. Media load paused." You can find a link to the video here: http://taggled.tv/video/353 Any hints on where I'm going wrong? I've tried changing the mime type on the ogg video to application/ogg as someone recommended this, but still no luck!

Todas as respostas (1)

more options

Can you try it without adding the crossorigin attribute to the video tag? Since your server is not responding with an Access-Control-Allow-Origin header, I think this may be causing a silent cross-origin fail.