Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut

Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.

Doesn't save Config setting: network.protocol-handler.expose.file

  • 1 balas
  • 1 memiliki masalah ini
  • 1 kunjungan
  • Balasan terakhir oleh asq

asq
asq
more options

In "about:config" I put network.protocol-handler.expose.file = false in order to open files and folders in external applications, not in FF. But when Firefox exits it deletes that setting from prefs.js And when Firefox starts and it is FALSE in prefs.js then it sets it to TRUE. How can I curcumvent that? I want it to stay FALSE. Thank you.

FF 27, and don't propose me to upgrade to Australis.

In "about:config" I put network.protocol-handler.expose.file = false in order to open files and folders in external applications, not in FF. But when Firefox exits it deletes that setting from prefs.js And when Firefox starts and it is FALSE in prefs.js then it sets it to TRUE. How can I curcumvent that? I want it to stay FALSE. Thank you. FF 27, and don't propose me to upgrade to Australis.

Solusi terpilih

I found solution: set "noscript.fixURI" = false (in "about:config" or in prefs.js). Problem was caused by NoScript over-defensive measures.

Baca jawaban ini dalam konteks 👍 1

Semua Balasan (1)

asq
asq Pemilik pertanyaan
more options

Solusi Terpilih

I found solution: set "noscript.fixURI" = false (in "about:config" or in prefs.js). Problem was caused by NoScript over-defensive measures.