לאתר זה תהיה פונקציונליות מוגבלת בזמן שאנו מתחזקים אותו לשיפור החוויה שלך. אם מאמר מסויים לא פותר את הבעיה שלך וברצונך לשאול שאלה, קהילת התמיכה שלנו מחכה לעזור לך ב־Twitter תחת ‎@FirefoxSupport וב־Reddit תחת ‎/r/firefox.

חיפוש בתמיכה

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.

מידע נוסף

How to stop Firefox from checking for add-on compatibility every time it opens?

  • 2 תגובות
  • 4 have this problem
  • 1 view
  • תגובה אחרונה מאת Dummy88

more options

How to stop Firefox from checking for add-on compatibility every time it opens?

How to stop Firefox from checking for add-on compatibility every time it opens?

פתרון נבחר

That can be a problem with the compatibility.ini file in the Firefox profile folder. Try to rename (or delete) the compatibility.ini file in the Firefox profile folder to see if that helps.

You can use this button to go to the currently used Firefox profile folder:

You can also check for problems with preferences.

Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

Read this answer in context 👍 1

כל התגובות (2)

more options

פתרון נבחר

That can be a problem with the compatibility.ini file in the Firefox profile folder. Try to rename (or delete) the compatibility.ini file in the Firefox profile folder to see if that helps.

You can use this button to go to the currently used Firefox profile folder:

You can also check for problems with preferences.

Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

more options

Deleting all the .js files in the profile cleared all the session start problems that I was experiencing following the update to 34.0.5