Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Mozilla サポートの検索

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

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Did plugin.load_flash_only get re-enabled in Firefox 55? I thought this was depricated in Firefox 53.

  • 3 件の返信
  • 4 人がこの問題に困っています
  • 2 回表示
  • 最後の返信者: cor-el

more options

I was troubleshooting an issue where Firefox was not loading an Extension as expected in Firefox 55 32bit. From looking at the Javascript calls the old Plugin which is still available was able to be loaded by Firefox. We found that plugin.load_flash_only was set to False on the affected browser. When we changed this back to plugin.load_flash_only = True, the extension then properly loaded.

I thought from documentation that the workaround was disabled in Firefox 53+? Was this recently changed or inadvertently re-enabled?

I was troubleshooting an issue where Firefox was not loading an Extension as expected in Firefox 55 32bit. From looking at the Javascript calls the old Plugin which is still available was able to be loaded by Firefox. We found that plugin.load_flash_only was set to False on the affected browser. When we changed this back to plugin.load_flash_only = True, the extension then properly loaded. I thought from documentation that the workaround was disabled in Firefox 53+? Was this recently changed or inadvertently re-enabled?

すべての返信 (3)

more options

Further testing showed that even toggling plugin.load_flash_only from False, to True, to False also works then as expected. So now unsure if this is only if the setting is set via prefs.js or mozilla.cfg as a default setting.

This issue only started occuring after 09/18.

more options

Probably a lingering after-effect on the 32bit version. :P

more options

Did you check the Browser Console for messages about this extension?