(*** This bug was imported into bugs.kde.org ***) Package: khtml Version: 3.0 (KDE 2.0) Severity: wishlist Compiler: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) OS: Linux 2.2.16-3 i686 (compiled sources) Hi When selecting back and forward konqi seems to first display the page from the top and then redisplay the page at the point previously viewed. It also seems to end up retrieving the page again. The redisplay seems unnecessary and detracts from the viewing. Also it seems that if we jump back or forward we shouldn't retrieve again the page unless it has expired. I spend a great deal of time navigating back and fortth and so I would appreciate this enhancement. Thanks Lou Nagy
"we shouldn't retrieve again the page unless it has expired" IMHO, when using back and forth, the page should _never_ be reloaded. It is actually only when the page has expired (happens all the time with dynamic sites), but that's not what I want. In this case, I'll press reload if I want to reload it. Otherwise, I want exactly the page I viewed without completely messing (poorly designed) website "application" and without reloading.
This is part of what I wrote at dot.kde.org. Sorry for the duplicate post. The original mesasge is at [http://dot.kde.org/1058698506/1058767773/1058775927/]. > Possibly it makes a GET with If-Modified-Since. Konqueror should NEVER reload the page when going back/forward because: 1. It involves network traffic, which is MUCH too slow in this case. Going back/forward must be fast, and must thus be handled completely local. 2. It is not what the user expects. The user expects to see the page as it was when he left it. The result should be equivalent to if the user viewed the page and opened a link in a new window and made the equivalent of browser-'back' by switching back to the previous window (Alt+Tab). Konqueror does not make a GET with If-Modified-Since in that case either, right?
Konqueror should not attempt to retrieve anything from the network when the user hits the back button. This is clearly a protocol violation. From RFC 2616 (the HTTP RFC): "In particular history mechanisms SHOULD NOT try to show a semantically transparent view of the current state of a resource. Rather, a history mechanism is meant to show exactly what the user saw at the time when the resource was retrieved." http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.13
Using 3.1.93. I couldn't find any situation where Konqueror refeched the page during forward / back operations or displayed it from the top. Also, since bug #59965 appears to be fine as well, I'd suggest the original reporter to test again.
for me, konqueror *always* at least checks that the page is up-to-date, hence triggering reloads for dynamic pages. This is wrong behavior and makes my going back and forth REALLY slow, plus it repeats some operations which result in submitting forms twice, etcetera.
Ok, I have set an iptables rule that logs all network activity ("iptables -A INPUT -j LOG --log-prefix iptables" then view with dmesg). I've opened several pages, both static and dynamic (such as a bugs.kde.org query or a webmail application that checks mail). Clicking on links, going back and forth repeatedly. No network activity at all. It seems however that on one instance where my history was really deep (like 10 entries), Konqueror did reload that very old page. Perhaps I should have a larger cache? As for the wheel spinning for a few moments, that is while the page is being rendered from cache, no network activity happens. So if you still see reloads or "checks if the page is up-to-date", you should: 1. update to the latest version of KDE from CVS, or atleast beta1 2. set up an iptables rule such as the above 3. find the exact site where this happens 4. report here with URLs and steps to reproduce.
Subject: Re: Back/Forward Page Display This logging thing is a great idea. Please try to set Konq's cache settings to "keep cache in sync". (i am using kde version is 3.1) DISCLAIMER: I am not using this setting now.
Sorry for late response, I was rather busy last week. Konqueror was in "keep cache in sync" mode, which is the default, all the time.
If there is no network traffic, this bug is a dup of bug 61290.
this bug can be related to bug # 61057 and/or bug # 59965
I think this can be closed. Konqueror does not refetch the page any longer - the other part of making "back" quicker is stated in bug #61290. I will close this soon if nobody disagrees.
*** Bug has been marked as fixed ***.