Hey all,Don't know how many others are suffering from slow page loads in FireFox on Warp/eCS... but the problem is actually page rendering (which is horrendously slow with the last few years of ports). The gang porting to OS/2 are trying to rectify it, but in the meantime, I have found some preference changes/additions that have helpe make FireFox, SeaMonkey, etc appear a lot faster on my system.
You may want to fool with the values a little depending on how fast your machine is (this one is 1.1GHz). Basically, it delays page rendering a bit - enough so that the whole document (on a fast connection) is already loaded in the browser, then laid out, and THEN rendered to the screen. It also affects rendering on pages where the content is not fully downloaded to the browser before screen rendering starts.
You may notice a 1 second delay on page loads (display) for minimal pages - but with how few minimal pages are out there, I dont mind. Also, on my system, even a minimal page (a frameset, 10 form values) still took longer to render, re-size, render, resize while getting the page from the server than the page delay I am using below.
YMMV
Hope this helps... it goes in your prefs.js - make sure the browser is closed when you put it in, otherwise the browser will overwrite the settings when it closes. OR you can manually enter each value using Preferential or similar Preferences editor while the browser is running.
Most of you probably wont have any of these in your prefs.js file - but since it is apparently in sorted order, you can double-check before you put them in. You CAN put them at the bottom of the file and the browser will order them the next time it is opened and closed.
Something else to keep in mind, if you have a Mozilla_Home directory set, you need to find the appropriate prefs.js file in those directories - the one in the browser directory (if it exists) is not the one the browser is using.
HTH,
Robert
user_pref("content.max.tokenizing.time", 3000000);
user_pref("content.notify.backoffcount", 5);
user_pref("content.notify.interval", 2000000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 2000000);
user_pref("nglayout.initialpaint.delay", 12120);
For the very curious, for details about what each does, just Google em...