189915 - javascript not interpreted in A HREF when middle clicking or opening in new window

Status: RESOLVED DUPLICATE of bug 55696

(SeaMonkey :: Tabbed Browser, defect)

Description

[Jason Kennerly]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2.1) Gecko/20021130

a link to "javascript:openWindow('Somewhere://SomeUrl.htm')" opens a new window
when clicked. 


Reproducible: Always

Steps to Reproduce:
1. visit the test page.
2. click the "this link" link and note the new window.
3. close the new window
4. now try middle-click, "open in new window", or "open in new tab"
Actual Results:  
Middle-clicking it fails, instead opens a new window with about:blank as the URL
'open in new window' and 'open in new tab' fail in a similar fashion.

Expected Results:  
In all honestly, I expected it to fail... 
This has bugged me about browsers for ages. When I first ran across this in the
late 1990s, what I expected was a result similar or identical to what happens
when one left clicks the link.

This exact bug is also present in most versions of MSIE and Netscape.

Either:
A. Javascript should instead be interpreted prior to opening the new window. If
a new window is to actually be opened by the javascript, it should be opened. If
a new window is NOT opened by the javascript, but rather some other function is
performed, then a duplicate of the current window should be opened.
or
B. The current window should be duplicated whenever a link containing javascript
is opened in a new window, then the javascript can be interpreted in a fresh
window without effecting the contents of the original window.

B seems easier to implement as well as "safer", but I dont honestly know. Until
then, one must manually open the duplicate window themselves...

Comment 1

[Ruslan Ismailov]

Maybe it is dupe of bug 138198? 

Comment 2

[Alfonso Martinez]

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