Closed Bug 65714 Opened 25 years ago Closed 24 years ago

Mozilla goes to user home page when opening new window with javascript

Categories

(SeaMonkey :: UI Design, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 65993

People

(Reporter: joe, Assigned: alecf)

References

()

Details

When mozilla is asked to open a new window as a result of a javascript command, the new window appears to first try to load the user's home page before openning the page that has been requested. This can create a very confusing set of dialog boxes if there is something special about a users home page (i.e. it is a https page) To reproduce. 1) set your home page to https://www.gnacademy.org/ 2) try to submit a bug for mozilla under bugzilla using the link from http://www.mozilla.org 3) when you press the button that causes the user login page to appear you should trigger the bug that causes multiple dialogs for self-signed CA's. This shouldn't happen at all. mozilla should go straight to the new window without touching https://www.gnacademy.org/
With which build are you seeing this?
was also reported in bug 11131
I just saw this on www.netscape.com (with the "Get Netscape 6" popup). Linux build 2001-01-16-08. My homepage is https:, so I got two alerts (entering/leaving secure site)... Make sure to remove any .netscape.com cookies you have so that you can reproduce it. setting status to NEW, and over to networking
Assignee: asa → neeti
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking
Ever confirmed: true
QA Contact: doronr → tever
Summary: Mozilla goes to user home page when opening new window → Mozilla goes to user home page when opening new window with javascript
Hrm, that is strange. Viewed from navigator.js, the URL passed in through the window's parameters property is loaded at the end of the function Startup, called at onload. Other than that, no URL is loaded. Could one of you try commenting out these two lines (near line 467): if (startPage) loadURI(startPage); and see what happens? Make sure you zip the new navigator.js back up in comm.jar or know how to edit installed-chrome.txt to by-pass the JAR files.
I've been seeing this on http://www.cnn.com online surveys using recent builds. I just now reproduced it on the main page voting in the survey about the baseball hall of fame. The popup window loaded with the results and then loaded my user home (slashdot) _after_ the survey results so that I ended up with the small window containing the slashdot.org homepage in it instead of the intended page. 2001011608/Mtrunk/Linux
Bug 65993 might be related (window.open("") loads home page instead of about:blank).
See bug 65993 for an explanation of what's going on. Fixing that should fix this bug, marking this depending on it.
Depends on: 65993
Target Milestone: --- → Future
mass move, v2. qa to me.
QA Contact: tever → benc
confirmed in build 2001070508 under linux
Reassigning to alecf, he's recently been working on this.
Assignee: neeti → alecf
Component: Networking → XP Apps
Vishy, who is covering for alecf during his sabbatical? This bug may be causing an activation problem that Bhuvan is investigating. Did anyone try jag's suggestion?
Blake's reading Alec's bugmail. Now all the bugs mentioned here that this could be a dup/depends of seem to be fixed. Is this bug itself also fixed?
Why does this bug have a future TM? If I am not mistaken, this is the one of the worst bugs I have seen. In my experience with the builds from past several days including 7/18/2001 Win 32 branch build, not only I get the home page when I click on certain links in mail msgs but also when I click on a web link. The problem occurs often enough that I think this would be a bug to fix before shipping the next major release from the NS branch.
What makes this problem a show stopper for me is that sometimes, the homepage opens **permanently** rather than the intended link.
I'll go over and talk to Kat about this one.
Keywords: nsbeta1
Target Milestone: Future → ---
Kat, the problem we are having right now, it's not only with JavaScript. I know that you know this, so my question is.. is this the proper place?
Marcio, you are right. The problem is not specific to JS. Let's open a new bug for it. I will write one and cc every one on this bug on it.
This sounds very much like a dupe of bug 65993. Marking it such. Kat, could you verify that this is indeed fixed? *** This bug has been marked as a duplicate of 65993 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.