Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Local html files that use Flash player will not work, other sites or same file uploaded works.

  • 2 Antworten
  • 1 hat dieses Problem
  • 27 Aufrufe
  • Letzte Antwort von Gerry_D

more options

When reviewing files on my computer, html that used flash player, they will not work, while "most" other sites that use the same type of player do work. If I upload the html to my domain, it works perfectly.

It used to work before the dreaded 56.0.1 (64-bit) update, I'm totally in FEAR of any more Firefox updates that crash the browser.

I have turned off my updates, so that is NOT an option, I need to fix what I have.

Anyone have a fix so I can again work with these html files to edit etc?

When reviewing files on my computer, html that used flash player, they will not work, while "most" other sites that use the same type of player do work. If I upload the html to my domain, it works perfectly. It used to work before the dreaded 56.0.1 (64-bit) update, I'm totally in FEAR of any more Firefox updates that crash the browser. I have turned off my updates, so that is NOT an option, I need to fix what I have. Anyone have a fix so I can again work with these html files to edit etc?

Geändert am von NoahSUMO

Ausgewählte Lösung

This is possibly because the file:// protocol is disabled for plugins.

You can set this pref to false on the about:config page.

  • plugins.http_https_only = false

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

Diese Antwort im Kontext lesen 👍 1

Alle Antworten (2)

more options

Ausgewählte Lösung

This is possibly because the file:// protocol is disabled for plugins.

You can set this pref to false on the about:config page.

  • plugins.http_https_only = false

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

more options

Thanks! Like I said it was a problem since the dreaded 56.0.1 (64-bit) update. It's working like before the update. As a bit of information to you, the extension for all of these files is .htm not .html , I don't know if that also was a minor determining factor. (I'll have to test that.) But back to the :config, http_https_only=true, one would think the local files, ones on the computer, would not be within that restraint. After all, their either written by a user or considered safe because of virus or trojan protection. Thanks Again!