[20926] in Athena Bugs
Re: mozilla: second window always blank
daemon@ATHENA.MIT.EDU (t. belton)
Fri Oct 18 11:26:15 2002
Date: Fri, 18 Oct 2002 11:26:11 -0400 (EDT)
From: "t. belton" <tbelton@MIT.EDU>
To: Camilla R Fox <cfox@MIT.EDU>
cc: <bug-infoagents@MIT.EDU>, <nisha@MIT.EDU>
In-Reply-To: <200210180533.BAA23818@red-herring.mit.edu>
Message-ID: <Pine.GSO.4.33L.0210181116510.8607-100000@iphigenia.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Camilla:
The second window is supposed to come up blank when she clicks on the
Mozilla icon again. That behavior is controlled by my 'mozilla' script. (I
have no control over the ctrl-N behavior, which is built into the
browser.)
It comes up blank because we can either start it blank or give it a
specific, known-in-advance URL, and unless the user gave a URL on the
command line (which we handle properly), we wouldn't know what URL to show
in it.
But the window should WORK - that's the important thing. If she can't type
in a URL or use the Home button, then something is wrong. This was working
the last time I tested it.
I'll go back and look at it again, and then we can try to figure out if
something special is going wrong just for her. It may be a profile
problem, but offhand I can't see how.
-Todd
On Fri, 18 Oct 2002, Camilla R Fox wrote:
>
> [This problem is experienced by Nisha, cc'd here; if you've got something
> to add, please let her know.]
>
> When mozilla is opened, the first window works normally; if we try
> to open a second window, either by clicking on the mozilla icon, or
> by hitting ctrl-n, it shows a blank white screen and empty URL bar.
> Any attempt to open a page, either by clicking on "home" or by entering
> the URL result in a pop-up, with a message to the effect of, "Can't open /
> no such file or directory" (paraphrased).
>
> We tried removing her multiple profiles, as well as moving aside the
> whole mozilla directory and letting mozilla convert a new one from her
> netscape 4 preferences; it seemed to make no difference.
>
> We were testing this on a cluster linux machine, but it apparently
> happens everywhere, ever since the switch to mozilla.
>
> -Camilla
>
