Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.
Archivado

I've upgraded to firefox 4/snow leopard and now my .avi's won't play using the quicktime plugin. What am I doing wrong?

manifold replied
manifold

I'm unable to play .avi's in Firefox 4 that worked fine in Firefox 3. I just get a blank page. I've also upgraded from Leopard to Snow Leopard (prior to upgrading Firefox) since the last time I viewed them.

I'm serving these files from my local harddrive so the url starts with file::

I believe these were displayed using the quicktime plugin. Firefox reports my current quicktime plugin as version 7.6.6

I need to get this working because I'm giving a talk soon, and I've been using references in my talk pdf to link to the movies.

==

Just checked, and my movies play fine in Safari. Crud. I'd rather not have to switch to Safari as my default browser. Yuk.

I'm unable to play .avi's in Firefox 4 that worked fine in Firefox 3. I just get a blank page. I've also upgraded from Leopard to Snow Leopard (prior to upgrading Firefox) since the last time I viewed them. I'm serving these files from my local harddrive so the url starts with file:: I believe these were displayed using the quicktime plugin. Firefox reports my current quicktime plugin as version 7.6.6 I need to get this working because I'm giving a talk soon, and I've been using references in my talk pdf to link to the movies. ====== Just checked, and my movies play fine in Safari. Crud. I'd rather not have to switch to Safari as my default browser. Yuk.

Modificadas por manifold el

Todas las respuestas (1)

Update: Turns out this is only a problem when the .avi is stored locally and served locally. I uploaded the file to a server and then pointed Firefox there. In that case it displays just fine. Weird.