161719 - Opening a URL in a Tab that was destined to be a new window fails by duping the same URL

Status: RESOLVED DUPLICATE of bug 142712

(SeaMonkey :: UI Design, defect)

Description

[David Wilson]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721
BuildID:    2002072104

Opening a URL in a Tab that was destined to be a new window fails by duping the
same URL as a Tab.



Reproducible: Always
Steps to Reproduce:
1.From the URL provided, selecting the link indicated by "Low send rates to
_anywhere in the world_" does not open a new window.
2.
3.

Actual Results:  Another tab duplicating the original tab is created.

Expected Results:  The new tab invocation to fail and a new window with the
desired URL  should appear.  Or a message/request confirming the user's intent.

Comment 1

[Jesse Ruderman]

The link you're talking about *is* a link back to the same page.  It has a
javascript onclick handler set up so that when you have javascript enabled and
click the link normally, it opens something in a new window instead of returning
to the same page.  The page is broken, because disabling javascript changes the
destination of the link.  I don't know if Mozilla can work around this problem.

See also:
bug  55696 "Open a JavaScript link in a new window"
bug 151142 modifier+click on a link (ctrl, shift) should not fire onclick event

(Note that bug 55696 is about real javascript links, not normal links that have
onclick handlers.)

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[:Hb]

Outdated report, original page probably changed. Duplicate of meta bug.