Bug 110430

Behaviour on 3.5 branch r575787 is as described. Not sure what the intended behaviour is though

Behaviour described confirmed KDE 3.5.5 / Kubuntu 6.10. Pattern appears to be that until the server for the 2nd site has responded it will refresh the original page.  After receiving a response it will refresh the 2nd site.

Preferred intended behaviour not clear.  If no response has been received, the user cancels the attempt & the page has not been updated, it will be counterintuitive to refresh the 2nd page.  However, if page request is ongoing it may make sense to refresh this current connection.

Anyone else?

Hi. I originally reported this bug a long time ago and forgot myself the reason I reported it. My example was probably a little strange and unhelpful but I think I was trying to make it easy to replicate without explaining why it is annoying in practice. Try this instead:

Example: 
Open konqueror .
Goto a website that normally takes a couple of seconds to load links (e.g. www.amazon.co.uk for me).
Click a link.
Hit F5 (reload) while the link is waiting to start loading (if the new page starts to render, try a slower website).

What happens:
The old page will be reloaded.

What I would expect to happen:
The request to load the clicked link should be repeated (and hopefully the clicked link should load and start rendering).

An actual scenario where this behaviour is bad is:
A user is on a slow website.
They click a link.
They wait.
The current page does not change because the website is slow.
They wait longer and think the website is very slow or the connection has 'broken' etc.
They click 'reload' to try to get the page to load properly (I've seen quite a lot of users do this personally).
Instead of the link they wanted loading, the original page loads.
This is confusing as sometimes the user will actually think the request has been resent (not understanding that the current page just re-rendered) and waits again for the page to load (when now, the page will never load).

I think sensible general behaviour would be:

if reload is clicked
  if a page is trying to load
    load the page that is trying to load
  else
    load the current page

This way, clicking stop and then reload will reload the original page, which makes sense as you are saying "stop trying to load the page I clicked on, now reload the page I can see".

Confirmed on kde 3.5.5. 

This bug also happens when you have no page loaded in konqueror (I have no home page loading by default) ((You can reproduce it by opening a new tab). Type in a site name, and before it loads, press F5. Konqueror refreshes to a blank page and no site in the location/address bar.

Behaviour still exists in 4.0.3/Kubuntu, although checking with Firefox3 it does the same thing there. I agree it's annoying though.

Confirmed even in 4.1 (trunk r802881).

Same problem as bug #123303

You cannot reload a page that has yet to be loaded ; so when you press reload without stoping the current load action, then the reload can only reload what is currently being shown! IOW, you cannot reload a pending action! However, if you first press stop and then press reload, then the previous action has been interuppted, so the reload should do what you all are stating it should.

You can test this behavior in any of the other major browsers (I did not test IE), and you get the same exact behavior. The only issue in Konqueror is that even if you press STOP and then RELOAD, it still reloads the old page. That needs to be addressed. Other than that it is a WON'T FIX.

Closing as WONTFIX as of comment #8.