Closed Bug 276252 Opened 20 years ago Closed 20 years ago

CTRL click / middle click on link in email message fails to open in browser

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 267378

People

(Reporter: symbiat, Assigned: sspitzer)

References

Details

(Keywords: regression)

I have CTRL click set in my preferences to open links in a new tab. However,
CTRL clicking on a link in an email message opens one tab then fails to open any
more after that.
On further investigation, it looks like CTRL click doesn't work at all for any
links in an email message. RIGHT clicking and selecting "Open in new tab" works
just fine. I have closed and restarted several times to verify.
I see this too -- 1.7.5, Win2K.  Working fine with same profile in 1.8a6-1217.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
*** Bug 276201 has been marked as a duplicate of this bug. ***
Updating summary per dupe
Summary: CTRL click on link in email message fails → CTRL click / middle click on link in email message fails to open in browser
*** Bug 276266 has been marked as a duplicate of this bug. ***
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20041228

I can confirm that the noted error happens on Linux on the latest 1.7.x branch,
but works fine on the latest trunk: Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.8a6) Gecko/20041228.

Note the 1.7.x version gives the following javascipt error:

JavaScript error:
chrome://communicator/content/contentAreaClick.js line 153: XPCNativeWrapper is
not defined
contentAreaClick.js was touched on the branch on 18/10/2004 by bug 249332 which
I can't access - security bug, but the changes introduced the XPCNativeWrapper.

It also was touched on 22/10/2004 by bug 265176 which I believe is a security
bug as well, but I don't think the changes would have caused this bug.

Also changing OS to all as that what this bug affects.
OS: Windows 2000 → All
Related to bug 267378?
Yep, this bug looks the same as bug 267378, therefore marking duplicate.

BTW: for anyone interested that bug has a patch in the review process for fixing
it as well.

*** This bug has been marked as a duplicate of 267378 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.