151833 - Tab browser window does not open when following a javascript "location.href" link

Status: VERIFIED DUPLICATE of bug 89296

(SeaMonkey :: Tabbed Browser, defect)

Description

[leadsides]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1a) Gecko/20020611
BuildID:    2002061104

I tried to open a tab window on a sponsored link from a Google search page by
control+left mouse clicking on the link.  A tab window did open, but the
originating window also redirected to the link.  I looked at their source code,
did some experimenting, and discoved that a tab window will not open when
following a link created by a javascript "location.href".  Instead, the original
window will redirect to the linked URL.  When javascript and html code are
present for the same link, a new tab window will open (because of the html), but
both it and the original window open to the linked url.  This may be related to
bugs #103843 and #138198, although there is no attempt to open a new javascript
window in the link.  The URL I included is a test page I set up to try this.

Reproducible: Always
Steps to Reproduce:
1.hold down control and left-click on a link created by a javascript
"location.href".
2.
3.

Actual Results:  No tab window opened.  Instead, the originating window followed
the link.

Expected Results:  Tab window would open to the link.  Originating window would
not change.

Comment 1

[Jesse Ruderman]

A javascript link (location.href=) activated by ctrl+click should open in a new
tab/window.  This is bug 55696, "RFE: 'Open a JavaScript link in a new window'".
 I know of no browser that gets this right, but I do consider it a bug.

But just fixing bug 55696 would cause the link to be opened in *two* new
tabs/windows: one for the link, and one for the javascript that activates when
you click anywhere in the advertisement.  I think this can only be fixed by
Google (bug 89296).  Google could fix this by making the entire advertisement a
real link (<a href>) using style="display: block".  Or they could simply ditch
the javascript assume users will figure out that the clickable part of the ad is
the part with the blue underlined text and the hand cursor.

Since a fix for bug 89296 would completely fix this bug while a fix for bug
55696 would not, I'm marking this as a duplicate of bug 89296.

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

Comment 2

[Jesse Ruderman]

We could stop sending ctrl+click events to pages (bug 151142).

Comment 3

[sairuh (rarely reading bugmail)]

marking verified as a duplicate.

if you decide to reopen this bug, please clarify why.

search string for bugspam removal: SalviaGuaranitica