Closed Bug 167941 Opened 23 years ago Closed 23 years ago

Cannot open a new tab for any on the links on this site

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 162393

People

(Reporter: sizemoresr, Assigned: jag+mozilla)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 On the site www.worthynews.com, I cannot open any of the links in a new tab. I've tried this using Red Hat 7.3 and WinXP SP 1 on Mozilla 1.1. Most of the links are cgi files, perhaps that's a problem. Every other site a frequent works fine, and so did this one until just recently. Reproducible: Always Steps to Reproduce: 1. go to www.worthynews.com 2. right click on any link. 3. choose open in new tab Actual Results: Nothing happens Expected Results: I expected a new tab to open for the link.
I logged this using a linux box with and older copy of mozilla. I want to assure you that they problem is in mozilla 1.2
Confirming with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910 But when you turn JavaScript off, it works. So I think the problem must be somewhere in the JavaScript
Using BuildID 2002090708 on WinXP. If you try doing a right click and open in new tab on the lead story you get the following in JS console: Error: focusedWindow._content.location has no properties Source File: chrome://communicator/content/contentAreaUtils.js Line: 59 The page is using an old version of pmenu from http://www.geocities.com/menulite/ current version is 2.5 not sure which version the page is using but it's not NS6+ aware.
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** This bug has been marked as a duplicate of 162393 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Was this duped against the correct bug as I can't see bug 162393? If that is the correct bug can we have some sort of hint to the problem?
it was. the problem is the js variable named content. as that variable is being used internally as well, there is a conflict. this can be exploited.
mass-verification of Duplicates. mail search string for bugspam: SolarFlaresAreTheCause
Status: RESOLVED → VERIFIED
Group: security
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.