Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
http://www.mozillazi...ml?article=6567
Quote
Thursday May 5th, 2005
The latest nightly builds of Mozilla Firefox include a new feature that significantly improves the speed of the Back and Forward buttons. When using Back and Forward in older builds, the page is retrieved from the local cache rather than the Internet but Gecko still has to reparse the HTML and use it to rerender the page, which can take a while with more complex documents. With this new feature, the rendered page is kept in memory, which makes Back and Forward performance much faster (almost instantaneous). In addition, going back or forward to a page cached in this way shows the page exactly how it was when you left it, in compliance with section 13.13 of RFC 2616.
The blazingly fast Back and Forward feature is currently disabled by default. See Chase Phillips' weblog post for instructions on turning it on. It is hoped it will be enabled by default in time for the release of Firefox 1.1. More technical details can be found in bug 274784 (no unnecessary comments please). Experience from other browsers (Opera, Internet Explorer and Safari have similar features) has shown that this is a tricky thing to get right without breaking a lot of pages.
While almost everyone approves of the faster performance, this feature is not without controversy. At the moment, the trunk is frozen in preparation for Mozilla 1.8 Beta 2 and checkins are supposed to be restricted and controlled. Some developers feel that such a major change should not be allowed to land at this time and have argued that it should have to wait until the start of the 1.9 release cycle (after Firefox 1.1). There are also concerns that the feature is rather buggy in its current state. Meanwhile, proponents of the new feature state that it would be costly to maintain it until the start of 1.9 development and have argued that it is best to get it in now so that it can be exposed to wide testing. These discussions have led to the feature being checked in but disabled by default, a compromise which we understand has left most developers basically happy.
If you find any bugs with the improved Back and Forward feature, please file them in Bugzilla. There should be no regressions when it's disabled, so please also file bugs if that's not the case.
The latest nightly builds of Mozilla Firefox include a new feature that significantly improves the speed of the Back and Forward buttons. When using Back and Forward in older builds, the page is retrieved from the local cache rather than the Internet but Gecko still has to reparse the HTML and use it to rerender the page, which can take a while with more complex documents. With this new feature, the rendered page is kept in memory, which makes Back and Forward performance much faster (almost instantaneous). In addition, going back or forward to a page cached in this way shows the page exactly how it was when you left it, in compliance with section 13.13 of RFC 2616.
The blazingly fast Back and Forward feature is currently disabled by default. See Chase Phillips' weblog post for instructions on turning it on. It is hoped it will be enabled by default in time for the release of Firefox 1.1. More technical details can be found in bug 274784 (no unnecessary comments please). Experience from other browsers (Opera, Internet Explorer and Safari have similar features) has shown that this is a tricky thing to get right without breaking a lot of pages.
While almost everyone approves of the faster performance, this feature is not without controversy. At the moment, the trunk is frozen in preparation for Mozilla 1.8 Beta 2 and checkins are supposed to be restricted and controlled. Some developers feel that such a major change should not be allowed to land at this time and have argued that it should have to wait until the start of the 1.9 release cycle (after Firefox 1.1). There are also concerns that the feature is rather buggy in its current state. Meanwhile, proponents of the new feature state that it would be costly to maintain it until the start of 1.9 development and have argued that it is best to get it in now so that it can be exposed to wide testing. These discussions have led to the feature being checked in but disabled by default, a compromise which we understand has left most developers basically happy.
If you find any bugs with the improved Back and Forward feature, please file them in Bugzilla. There should be no regressions when it's disabled, so please also file bugs if that's not the case.
Back to top
