Bug 59966

Summary: Should not refetch page for saving
Product: [Applications] konqueror Reporter: Simon Huerlimann <simon.huerlimann>
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: esigra
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Simon Huerlimann 2003-06-17 21:43:42 UTC
Version:            (using KDE KDE 3.1.2)

Am Dienstag, 17. Juni 2003 19.43 schrieb Andras Mantia:
> On Tuesday 17 June 2003 20:00, Eric Laffoon wrote:
> [...]
>
> > Also some pages are set up to refresh every so often, like
> > news pages. You can be reading a Yahoo news page and see it reload. This
> > would be done with Javascript. These are the likely reasons. You can
> > increase your cache size and disable Javascript for those pages that
> > reload themselves.
>
> I find it a little dirty to do it. Can't be Konqueror a little more
> intelligent, and if a page ask to reload when the connection is down, do
> not obey the reload and live the page in the current state?
>
> Andras

I would even vote to *always* save the page without reloading. Not just to 
keep the internet healthy, but you normaly want to save, what you *see*, not 
what the url at the moment of saving points to.
Example: I open up a news page. Looks interesting, but I have to take a 
shower. After comming back, I decide to read the article on my notebook in 
the train. So I just save the page to a file and move it. But opening up the 
page in the train will show another news. The page just during my shower!

What about printing by the way? Does it also initiate a refetch?

Simon
Comment 1 Simon Huerlimann 2003-06-17 21:47:24 UTC

*** This bug has been marked as a duplicate of 59965 ***