47072 - Limited functionality if stopped while retrieving new page

Status: VERIFIED DUPLICATE of bug 5569

(Core :: DOM: Navigation, defect, P3)

Description

[Jonas Svensson]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20000728
BuildID:    2000072808

If page loading is aborted at the right moment the current page will stop
working. Ie it is no longer possible to follow links.

Reproducible: Always
Steps to Reproduce:
1. Open up www.cnn.com.
2. Follow one link.
3. Go back to first page.
4. Click another link.
5. Wait for the forward arrow to be greyed out.
6. Click stop before the next page is loadad and the current page is still there.

Actual Results:  The current page is still visible but no links works. The
window is not updated when other windows are moved around in front of it.

Expected Results:  Links should still work. The window should be updated when
moving other windows around in front of it.

Comment 1

[Mats Palmgren (inactive)]

*** Bug 47073 has been marked as a duplicate of this bug. ***

Comment 2

[Daniel Bratell]

Conmfirming. I didn't find any duplicate bug but I can't guarantee there isn't 
one. 

Reassigning to Docshell which seems to be the most obvious component to blame.

Comment 3

[Tomer Brisker]

Could reproduce on Linux 3009. OS should be all.

Comment 4

[Adam Lock]

When you say the page is still there, is it *really* the page or just garbage? 
If you move another window over the browser, does the page refresh or do you get 
a trail a crap left by the window you dragged over it?

If yes, then it's likely that this is a duplicate of bug 5569. Basically, you've 
managed to hit stop after the document is removed, but before the old one is 
reloaded. The browser has no content and doesn't do any painting at all.

Please confirm.

Comment 5

[Jonas Svensson]

No refresh. Would be good if the window could be blanked out instead. I find
this behaviour quite confusing.

Comment 6

[Adam Lock]

Okay, it sounds like a duplicate alright, so I'm marking it as such. Jonas, 
you're right that the content should be blanked out. The problem is that the 
window is rendered by a content viewer, but if there's no content then there's 
no content viewer to paint the window, hence its dirty.

The other bug will have to figure the best way to fix that one.

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

Comment 7

[Jonas Svensson]

Fine by me. Thank you.

Comment 8

[Blake Ross]

vrfy dup based on reporter's comments