Closed
Bug 84286
Opened 24 years ago
Closed 23 years ago
[RFE] Save complete document in cache instead of source for better performance (Cache DOM & Layout)
Categories
(Core :: DOM: Navigation, enhancement)
Core
DOM: Navigation
Tracking
()
Future
People
(Reporter: patrick, Assigned: jud)
References
()
Details
(Keywords: helpwanted, perf)
When you use the back button to revisit a previous page and you have left the
previous page at the bottom, then the previous page is first displayed from top
and only later scrolled down to the bottom where one has left it before.
Steps to reproduce:
Go to http://www.spiegel.de
Scroll down to the bottom
Select an article
On the new page, hit the back button
Result:
The browser loads the previous page from the cache (which is horribly slow)
The page is rendered top to bottom and the top is at first displayed
As soon as the bottom is ready, the page scrolls down automatically, leading to
a visible jump.
Expected result:
The browser loads the screen representation of the previous page from the cache
(which can be horribly fast)
The page is instantaneously displayed the same way you left it without visibly
jumping from top to bottom.
Check Opera for how they are doing it.
This is more closely related to session history. It's not a cache bug. Changing
component and owner.
Assignee: gordon → radha
Component: Networking: Cache → History: Session
QA Contact: tever → claudius
Comment 3•24 years ago
|
||
WORKSFORME
Platform: PC
OS: Windows NT
Mozilla Build: 2001062815
Marking as such.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Sorry, doesn't work at all. Just tried 2001071604 build on NT.
The page is rendered from scratch and displayed top-bottom. Once the previous position is reached again, the display jumps down.
I don't know if you don't see it on a 1 GHz machine because everything is so quick, but on my PII it is very, very disturbing. Again, I recommend comparing with Opera. Very smooth, no jumps. I assume they don't cache the HTML but the final rendered representation of the page, so they don't have to do it again.
reopened bug
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 6•24 years ago
|
||
To get the desired effect, mozilla needs to cache the entire document instead of
just the source and other stuff like form values and scroll positions, (which it
does right now). This is a major feature. This feature doesn't belong to Session
History either. But not sure where it should go. Giving it to Jud for now.
Assignee: radha → valeski
Summary: going back in history makes cached page jump → [RFE]Save complete document in cache instead of source for better performance.
Target Milestone: --- → Future
This bug sounds very similar to Bug 111036, should one of these get duped?
Comment 8•24 years ago
|
||
*** Bug 111036 has been marked as a duplicate of this bug. ***
Comment 9•24 years ago
|
||
Marc, should be this moved to Layout (where duped bug 111036 assigned to you
belongs)?
(Changing bug properties regarding dupe)
Keywords: helpwanted,
perf
OS: Windows NT → All
Hardware: PC → All
Summary: [RFE]Save complete document in cache instead of source for better performance. → [RFE] Save complete document in cache instead of source for better performance (Cache DOM & Layout)
Updated•24 years ago
|
Keywords: mozilla1.1
Comment 10•23 years ago
|
||
*** This bug has been marked as a duplicate of 38486 ***
Status: NEW → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → DUPLICATE
Comment 11•23 years ago
|
||
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•