Search Support

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.

Learn More

Why canI not change places.history.expiration.transient_current_max_pages in about:config?

  • 2 iimpendulo
  • 3 inale ngxaki
  • 1 view
  • Impendulo yokugqibela ngu cor-el

more options

OK this is strange: I go into about:config (firefox 32.0.3 running under Windows XP SP 2), and the value is locked at 26794 - if i try to modify it the modify box comes up, but no matter what number i enter it stays at 26794.

ALSO, i am using CUSTOM SETTINGS for privacy and i have checked off CLEAR HISTORY WHEN FIREFOX CLOSES, then under settings i check off CACHE and BROWSING AND DOWNLOAD HISTORY to be cleared, BUT after i close firefox and return, my history is not cleared. The only way i can delete history is to manually enter it and delete it. IDEAS???

OK this is strange: I go into about:config (firefox 32.0.3 running under Windows XP SP 2), and the value is locked at 26794 - if i try to modify it the modify box comes up, but no matter what number i enter it stays at 26794. ALSO, i am using CUSTOM SETTINGS for privacy and i have checked off CLEAR HISTORY WHEN FIREFOX CLOSES, then under settings i check off CACHE and BROWSING AND DOWNLOAD HISTORY to be cleared, BUT after i close firefox and return, my history is not cleared. The only way i can delete history is to manually enter it and delete it. IDEAS???

All Replies (2)

more options

Hello mermaid1966,

Your issue seems a bit more complicated and requires more investigation. We're currently looking into it and we'll get back to you with more details ASAP. Please understand that escalations can take up to 72 hours for a response, but no longer.

more options

The places.history.expiration.transient_current_max_pages pref is a read-only pref that shows the result of Firefox calculating how many pages you can safely save on your computer without affecting performance.

See Marco Bonardo's blog about this: