144587 - clicking javascript: link should not stop loading page

Status: RESOLVED DUPLICATE of bug 130265

(Core :: Networking, defect)

Description

[Jesse Ruderman]

Clicking a javascript: link that doesn't load another page should not stop
loading the current page.  Fixing this bug would make it easier to use
bookmarklets and interact with pages that use javascript:window.open() links.

Comment 1

[Jesse Ruderman]

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

Comment 2

[Jesse Ruderman]

The dup has a good testcase:
http://www.chez.com/zazoucosplay/galerie_014.html

Comment 3

[Andrei Boros]

Possibly related to this bug is the following behaviour I wanted to report:

When a page is loading and contains javascript window.open : 
while the page loads, if the user clicks on the link, page load stops and 
nothing happens. Subsequent clicks yield the same result.
Same result is achieved by pressing Stop before page finished loading.

Page has to be reloaded and user has to wait until the page finishes properly to 
use such links.

Comment 4

[benc]

Can we get specific steps using the current URL or the example in #2?

I think I know what you are saying, but my connection might be too fast to
simulate this correctly.

I'm not sure what is being asked for makes sense. If you are loading a page, and
you click on any link in that page, then the current page load stops, because
the browser jumps to the new link.

Comment 5

[Doug Turner (:dougt)]

this sounds like a major change to how Mozilla loads uri's.  I am futuring.

Comment 6

[jsp]

This is worth fixing. I've been seeing this intermittently for a really long
time, but only recently figured out what the problem is. It can cause users to
have to repost form data in order to use a page, which can have all sorts of
unintended consequences on, say, e-commerce sites.

In my case, I use anchors with href="javascript:void(0)" to enable tab
navigation among elements in my page. Once the page loads, I establish DOM event
handlers for active elements. If one of the anchors is activated while the page
is loading, the page never finishes loading, and is crippled by the absence of
its event handlers. The only workaround I can envision is pretty horrible: hide
the links until the page is completely loaded.

Comment 7

[Boris Zbarsky [:bzbarsky]]

See discussion starting at bug 130265 comment 21.

Comment 8

[Boris 'pi' Piwinger]

Let me see if I get this correctly. Comment 3 describes my problem and I am not
sure this is the bug I am looking for. I have a page with many images which are
generated on the fly which takes a while (you need a login to that page which is
in German, you can get a login for free:
http://web.consors.de/watchlist/WatchlistServlet)

Before all the little images are loaded you cannot click on the links which look
like this:
javascript:popupFinanzinfos('http://info.consors.de/financeinfos/snapshot.do?ID_NAME=WKN&ID=915298&EXCHANGE=FRA',
800, 600, 'finanzinfos');
which is essentially a windows.open. As described in comment 3 and the original
report the page stops loading (i.e. the not yet loaded images don't load) and
maybe worse there is no way to get the links working later one except for newly
loading the page, i.e. firing another POST.

If this is the right bug for this, it is at least major, if not critical since a
basic function completely fails.

Also I doubt this is the right component.

pi

Comment 9

[Jesse Ruderman]

Andrei (comment 3) and pi (comment 8),
- Bug 101190 covers not being able to use javascript: links that open new
windows while a page is loading.
- This bug covers images not finishing loading if you click a javascript: link
while a page is loading, among other things.  This bug is also present in IE.

Comment 10

[Boris 'pi' Piwinger]

Thanks. So it remains here that the page does not fully load. So this is in no
way minor (setting normal), might be major, though.

pi

Comment 11

[Jesse Ruderman]

WFM in Firebird 05/22.  I tested the javascript: links on
http://aoltvlistings.netscape.com/ and a few bookmarklets.

jst, maybe you fixed this when you fixed bug 130265 or bug 205989?

Comment 12

[jsp]

WFM with Mozilla 1.4rc1 in Windows 2000, using my own internal test case.

Comment 13

[Johnny Stenback (:jst)]

Yup, fixed indeed. This was actually a dup of bug 130265.

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

Comment 14

[benc]

Cool. I think we a actually have a couple of bugs running around in networking,
disguised as this... I'll find them an dupe them.