Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

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

  • 2 Mbohovái
  • 2 oguereko ko apañuãi
  • 156 Hecha
  • Mbohovái ipaháva 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?

Ñemoĩporã poravopyre

Opaite Mbohovái (2)

more options

Ñemoĩporã poravopyre

Try Locking preferences .


thank you

more options

That should be OK.

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