Closed Bug 180534 Opened 23 years ago Closed 23 years ago

improve back / forward performance

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 38486

People

(Reporter: sspitzer, Assigned: asa)

Details

(Keywords: perf)

improve back / forward performance here's mike lee's idea: from http://www.exitspace.net/mike/blog/archives/2002_11_01_mikelee_archive.html#84516896 Reading this thread about opera 7 [*] and someone mention how much faster opera is at showing the page when you click back. I thought of something, it's based on the similar idea of keeping the back page in memory (sorry I can't find it, but I know it's in bugzilla). But my idea is a hack, it doesn't require modification to mozilla's core engine, it's optional (ie, it can be turned off easily) and it should be easy to do. The idea is to hae a 'invisible' tab for each tab storing the page before it. So when user click on a link on the page the current page is stored into that invisible tab and the visible tab loads the page. Or make current tab invisible and create a new one at it's position to load the page, or any other method based on the same idea. Then clicking back should be fast just like switching tab. [*] http://www.mozillazine.org/forums/viewtopic.php?t=676
devil advocate: this idea is like the cached compose window, and we should just fix it the right way.
Keywords: perf
Seth: Do you saw bug 38486 ?
Right, I knew there was another bug on this (and it had already been discussed to death). Let's discuss there, since all the interested people are cc:ed. *** This bug has been marked as a duplicate of 38486 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.