78521 - clicking an URL doesn't stop previous from loading

Status: VERIFIED WORKSFORME

(Core :: Networking, defect, P3)

Description

[David Härdeman]

BuildID:    2001050104

If im on a fast web (local for instance), and click an external link in my
bookmarks, and before the DNS is complete, click a local link on the page, the
local page will load and when the DNS is done the other page will start loading

Reproducible: Always
Steps to Reproduce:
1. Go to fast web site
2. Click external (slow) link in bookmarks
3. Before DNS is done, click local link


Actual Results:  Local page is loaded first and sometime later when DNS is done,
remote will load

Expected Results:  Clicking a new link will cancel all previous clicks

I'm not sure if DNS and bookmarks have anything at all to do with it, it might
be so general that clicking links in order slow first and then fast will ive the
same experience. Guessing this will be cross-platform but I only have NT to test on

Comment 1

[Boris Zbarsky [:bzbarsky]]

ccing hyatt, since this seems related to things he's been working on.

Comment 2

[neeti]

Need a testcase to reproduce this.

Comment 3

[benc]

mass move, v2.
qa to me.

Comment 4

[benc]

David,

Can you give us a specific example, that includes URL's, prefereably from a
public site?

Comment 5

[David Härdeman]

Well, 
thats kinda hard to do since what's regarded as a "fast" and a "slow" webserver 
would depend on where you are located. If you're at Netscape in the US I'd guess 
bookmarking a minor overseas server would do. Then create a page (can be on your 
own HD) with a link to (for instance) some simple page within the mozilla.org 
domain.

(The way I found this strange behaviour was by looking at a page in out local 
intranet, then clicking a bookmark for some external slow server. I then 
changed my mind before the page started loading and instead clicked a link to 
another internal page, which of course loaded almost immediately). I dunno if I 
make any sense here? :-)

Comment 6

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 7

[David Härdeman]

OK, closing this one as I can't reproduce it any more with a recent version of
Mozilla regardless of platform (at least I've tried on Win2K, WinNT, Win98, Linux)

Comment 8

[benc]

david:
You are making sense, and actually there are two areas that should be tested,
ideally.

The first is to break in while waiting for a slow DNS server to respond. This is
hard to reproduce regularly, because your local DNS server would cache the response.

The second is to break in while waiting for either the TCP connection
establishment to occur (the three-way handshake) or waiting for the request to
complete. 

These might be hard to test, but I'm going to put them on my list. Thanks for
pointing this out.