Closed Bug 411370 Opened 18 years ago Closed 2 years ago

mobile specific all.js changes.

Categories

(Core :: General, defect)

x86
macOS
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: dougt, Unassigned)

Details

(Keywords: mobile)

There are many preference based changes we can make for mobile. This is the set I have been using for a while: http://lxr.mozilla.org/mozilla1.8/source/minimo/customization/all.js?raw=1 We should sort through this and have a all.js patch for mobile.
much of that link is duplication of the all.js file. The important parts: // Where do we want to send people when they use keyword searches. This sends them to a transcoder (google's). pref("keyword.enabled", true); pref("keyword.URL", "http://www.google.com/xhtml?q="); // no disk cache pref("browser.cache.disk.enable", false); pref("browser.cache.disk.capacity", 0); // small memory cache pref("browser.cache.memory.enable", true); pref("browser.cache.memory.capacity", 512); // no ssl disk cache pref("browser.cache.disk_cache_ssl", false); // Some session history pref("browser.sessionhistory.max_entries", 3); // Fastback caching - if this pref is negative, then we calculate the number // of content viewers to cache based on the amount of available memory. pref("browser.sessionhistory.max_total_viewers", 0); // we need to tweak his as mobile runs slower pref("dom.max_script_run_time", 60); I am sure that there are others. This doesn't include the network.http* changes which we should test.
can you split this up in to separate bugs for specific issues?
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.