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.

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.

Why does Firefox set network.protocol-handler.expose.(protocol) to "true" on every start?

  • 2 antwurd
  • 2 hawwe dit probleem
  • 110 werjeftes
  • Lêste antwurd fan cor-el

more options

I want to make FF open "file://"-links with the Windows Explorer. It works if I set "network.protocol-handler.expose.file" to false and "network.protocol-handler.external.file" to true. But "network.protocol-handler.expose.file" is missing in about:config after a restart. So i've set it in my user.js. Now I can see the variable but its always set to true no matter what stands in my user.js. Why is FF overriding my config?

I want to make FF open "file://"-links with the Windows Explorer. It works if I set "network.protocol-handler.expose.file" to false and "network.protocol-handler.external.file" to true. But "network.protocol-handler.expose.file" is missing in about:config after a restart. So i've set it in my user.js. Now I can see the variable but its always set to true no matter what stands in my user.js. Why is FF overriding my config?

Keazen oplossing

Alle antwurden (2)

more options

Keazen oplossing

Try Locking preferences .


thank you

more options

That should be OK.

Firefox should store the protocol settings in the mimeTypes.rdf file.