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.

Narrator doesen't show up anymore in reader view. <about:config> details inside

  • 3 antwurd
  • 1 hat dit probleem
  • 26 werjeftes
  • Lêste antwurd fan Luca

Luca
Luca
more options

Hi, I have 61.0.2 (64 bit windows 10)

Narrator doesn't show the icon ANYMORE. I used it daily, didn't change anything recently BUT only followed this guide to disable WebRTC

In short: 

   Enter "about:config" in the firefox address bar and press enter.
   Press the button "I'll be careful, I promise!"
   Search for "media.peerconnection.enabled"
   Double click the entry, the column "Value" should now be "false"
   Done. Do the WebRTC leak test again.

   media.peerconnection.turn.disable = true
   media.peerconnection.use_document_iceservers = false
   media.peerconnection.video.enabled = false
   media.peerconnection.identity.timeout = 1

is this the reason, is this a good thing after all?

Hi, I have 61.0.2 (64 bit windows 10) Narrator doesn't show the icon ANYMORE. I used it daily, didn't change anything recently BUT only followed this guide to disable WebRTC In short: Enter "about:config" in the firefox address bar and press enter. Press the button "I'll be careful, I promise!" Search for "media.peerconnection.enabled" Double click the entry, the column "Value" should now be "false" Done. Do the WebRTC leak test again. media.peerconnection.turn.disable = true media.peerconnection.use_document_iceservers = false media.peerconnection.video.enabled = false media.peerconnection.identity.timeout = 1 is this the reason, is this a good thing after all?

Keazen oplossing

THE PROBLEM WAS: 

privacy.resistFingerprinting = true


setting it back to " = false " RESTORED the NARRATOR

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (3)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Well, if you reverse those changes -- you can right-click > Reset to restore the default values -- does the narrator work again? You could try reversing one at a time to see which one is (or which ones are) the issue.

Here is a thread for VPN users about WebRTC leak prevention that may provide the protection you want without completely breaking things you don't need to break:

https://www.reddit.com/r/firefox/comments/8hjh3h/google_voice_psa_if_you_have_been_recently_having/

Luca
Luca Fraacheigener
more options

jscher2000 said

Well, if you reverse those changes -- you can right-click > Reset to restore the default values -- does the narrator work again? You could try reversing one at a time to see which one is (or which ones are) the issue. Here is a thread for VPN users about WebRTC leak prevention that may provide the protection you want without completely breaking things you don't need to break: https://www.reddit.com/r/firefox/comments/8hjh3h/google_voice_psa_if_you_have_been_recently_having/

thank you, I did it already, this is why I asked here in the 1st place. I uploaded a 2nd immage to show the only modified strings in about:config : media.

anyway it was 

privacy.resistFingerprinting = true.

that caused the problem

Bewurke troch Luca op

Luca
Luca Fraacheigener
more options

Keazen oplossing

THE PROBLEM WAS: 

privacy.resistFingerprinting = true


setting it back to " = false " RESTORED the NARRATOR