Note that the places.history.expiration.max_pages pref only makes it possible to keep more history items and doesn't actually have to do with the number of days to keep.

In Firefox 3 you could specify how many days to keep, but those prefs no longer work and you can reset them on the about:config page if you still have them.

• http://blog.bonardo.net/2010/01/20/places-got-async-expiration

• http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/nsPlacesExpiration.js

It does apply to the latest release, yes?

Yes.

See:

• http://mxr.mozilla.org/mozilla-release/source/toolkit/components/places/nsPlacesExpiration.js#78
• http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/nsPlacesExpiration.js#45

hi on your code, I can not find this entry: places.history.expiration.max_pages Is it different name now?

No the code splits it over two lines.

One line to define the pref branch #76 and #85 for the max_pages

• 76 const PREF_BRANCH = "places.history.expiration.";
• 85 const PREF_MAX_URIS = "max_pages";
• 768 this._urisLimit = this._prefBranch.getIntPref(PREF_MAX_URIS);

Ok thank you.

is it part of the full source code? where is the full source code?

You can get the source code via links on the web page:

• https://developer.mozilla.org/Download_Mozilla_Source_Code

• ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/14.0.1/source/

Thank you.

Are add-ons source codes similar to Firefox source code?

Add-ons are packed in a ZIP archive with and .xpi file extension.
Most add-ons consists only of JavaScript and XUL code that are readable, but may also contain binary components without a source code.

• https://developer.mozilla.org/en-US/docs/Extensions
• https://developer.mozilla.org/en/Extension_Packaging

thank you!

The binary components should be written in java?

And thank you for adding useful links in your posts :)