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’.

Learn More

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
  • 187 werjeftes
  • Lêste antwurd fan cor-el

Koopz
Koopz
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

Try Locking preferences .


thank you

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (2)

ideato
ideato
more options

Keazen oplossing

Try Locking preferences .


thank you

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

That should be OK.

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