Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

mozilla.cfg doesn't work version 48

  • 5 답장
  • 5 이 문제를 만남
  • 1 보기
  • 최종 답변자: smithd4

more options

Using the following doesn't do anything to the about:config settings in firefox:

mozilla.cfg with just the following:

// lockPref("app.update.enabled", false);

This doesn't change the setting from true to false or dither it out as locked? Does this method not work for version 48?

I do have the local-settings.js file with the following under defaults/pref:

// pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0);

Help!!!

Using the following doesn't do anything to the about:config settings in firefox: mozilla.cfg with just the following: // lockPref("app.update.enabled", false); This doesn't change the setting from true to false or dither it out as locked? Does this method not work for version 48? I do have the local-settings.js file with the following under defaults/pref: // pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0); Help!!!

선택된 해결법

I can't believe it, the problem was I needed to be using a single ' in the js file not regular double quotes " that I see on just about everything I have searched on. Arrrgh, very frustrating. It works now.  :-)

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (5)

more options

Have you always had the // at the beginning of those lines? In JavaScript, that would turn the line from a command into a comment, which should deactivate it. ??

more options

Everything I have read says to comment out the first line of the file...is that not correct?

more options

// is on its own line but the formatting in the question changed it to the same line.

more options

Oh, okay.

I'm still on Firefox 47 and haven't heard about any changes related to autoconfig in Firefox 48, so hopefully someone else knows what's going on.

more options

선택된 해결법

I can't believe it, the problem was I needed to be using a single ' in the js file not regular double quotes " that I see on just about everything I have searched on. Arrrgh, very frustrating. It works now.  :-)