X
Tap here to go to the mobile version of the site.

Support Forum

FF 71. Cannot change value in setting places.history.expiration.transient_current_max_pages

Posted

In about:config I set the value to 2147483647 on one PC and 999999999 on another. Now it's not possible to change the numbers. I see this setting in the prefs.js file, but have not changed it there yet. Why is that?

Am I generally picking the right settings so that, in fact, the browser never deletes the pages I visited? Now I still use FF 56.0.2 and the places.sqlite file is 300 MB in size, FF 71 happily accepted this file and my history remained in place.

In about:config I set the value to 2147483647 on one PC and 999999999 on another. Now it's not possible to change the numbers. I see this setting in the prefs.js file, but have not changed it there yet. Why is that? Am I generally picking the right settings so that, in fact, the browser never deletes the pages I visited? Now I still use FF 56.0.2 and the places.sqlite file is 300 MB in size, FF 71 happily accepted this file and my history remained in place.

Modified by booya

Chosen solution

Note that places.history.expiration.transient_current_max_pages is a read-only preference.

Like you posted, you have to create a new Integer pref named places.history.expiration.max_pages if you want to modify the automatically calculates number of pages as shown in places.history.expiration.transient_current_max_pages.

Read this answer in context 1
Quote

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36

More Information

Question owner

Sorry, Everything went from setting - places.history.expiration.max_pages

Sorry, Everything went from setting - '''places.history.expiration.max_pages'''
Was this helpful to you?
Quote
cor-el
  • Top 10 Contributor
  • Moderator
17865 solutions 161655 answers

Chosen Solution

Note that places.history.expiration.transient_current_max_pages is a read-only preference.

Like you posted, you have to create a new Integer pref named places.history.expiration.max_pages if you want to modify the automatically calculates number of pages as shown in places.history.expiration.transient_current_max_pages.

Note that places.history.expiration.transient_current_max_pages is a read-only preference. Like you posted, you have to create a new Integer pref named places.history.expiration.max_pages if you want to modify the automatically calculates number of pages as shown in places.history.expiration.transient_current_max_pages.
Was this helpful to you? 1
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.