Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Youtube doesn't work on https: in Firefox 20

  • 2 antwurd
  • 32 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan Reiser

Reiser
Reiser
more options

YouTube stop working via https after I updated from Firefox 19.0.2 to 20.0.1. But via http it works fine. Also embedded YouTube doesn't work on sites that use src=https:// and works on that use src=http:// ones. Everything working fine as I roll back to 19.0.2 and stop working after re-update. I've tested the Safe Mode — the same effect, doesn't help. I've tested new profile — everything seems fine, YT works via http and https. So, if there's no clear solution to my problem, is there any way to dump full 'about:config'-config to diff with default one?

YouTube stop working via https after I updated from Firefox 19.0.2 to 20.0.1. But via http it works fine. Also embedded YouTube doesn't work on sites that use src=https:// and works on that use src=http:// ones. Everything working fine as I roll back to 19.0.2 and stop working after re-update. I've tested the Safe Mode — the same effect, doesn't help. I've tested new profile — everything seems fine, YT works via http and https. So, if there's no clear solution to my problem, is there any way to dump full 'about:config'-config to diff with default one?

Keazen oplossing

hello reiser, this issue is likely caused by the following configuration you've performed in about:config: security.mixed_content.block_active_content: True & security.mixed_content.block_display_content: True.

Dit antwurd yn kontekst lêze 👍 3

Alle antwurden (2)

philipp
philipp
  • Moderator
more options

Keazen oplossing

hello reiser, this issue is likely caused by the following configuration you've performed in about:config: security.mixed_content.block_active_content: True & security.mixed_content.block_display_content: True.

Reiser
Reiser Fraacheigener
more options

Thank you very much! I'm very glad solution have been found so easily. It seems odd to me this settings had no effect in FF19.

Bewurke troch Reiser op