This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

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

  • 2 antwoorde
  • 1 het hierdie probleem
  • 27 views
  • Laaste antwoord deur 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?

Gewysig op deur NoahSUMO

Gekose oplossing

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.

Lees dié antwoord in konteks 👍 1

All Replies (2)

more options

Gekose oplossing

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!