Empty page/Incorret size when starting two pages from an external source

RESOLVED EXPIRED

Status

SeaMonkey
UI Design
RESOLVED EXPIRED
15 years ago
8 years ago

People

(Reporter: Nahor, Assigned: jag (Peter Annema))

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

15 years ago
Build 2002100808
WinXP
Bi-Athlon 1900+

I'm using Trillian (http://www.ceruleanstudios.com) with the News plugin (RSS
reader). When I double click on a news, it opens the default browser to page of
the article. If Mozilla wasn't loaded and I try to open two articles, I get a
weird result:
1. The mozilla windows are slightly bigger than usual. It usually the size of
the desktop.
2. The first window to appear is blank, uses the default mozilla icons instead
of the browser icon and the navigation bar is empty
3. The second window has the first article loaded correctly but has the
navigation bar empty too.
4. I can't enter anything in the navigation bar of those two windows.

I stumble on this bug quite easily but fails to reproduce it reliably. I don't
know if the fact that I have a bi-processor helps or not.

Steps to reproduce:
1. Make Mozilla your default browser
2. Exit any Mozilla session, maybe even Quicklaunch (I don't use it)
3. Maybe copy some big files or open some big applications so that Mozilla isn't
in the Windows file cache. I always get the bug when Mozilla has been closed for
a while.
4. Open quickly two webpages. I got it to work a couple times when I tried to
open a local html file.

Actual results:
  see above and the two screenshots
  

I suspect a problem with the "one mozilla instance" system (DDE?). Somehow,
Mozilla accepts the second URL request when it's not quite ready to handle it.
Since the second window has the first article, so I assume that the first window
to appear (the empty one) is for the second article. 
I speculate that a Mozilla thread thinks that something is ready while it isn't,
so when it tries to get the html page, it fails but not deterred by that, it
still displays a window. 
As for the first link, the thread handling it knows that the "something" isn't
ready and so waits for it before loading the page. That would explain why the
*first* article shows up in the *second* window.
But this speculation doesn't explain the unresponsive navigation bar nor the
unsual size of the window.


PS: And if someone can come up with a better summary.....
(Reporter)

Comment 1

15 years ago
Created attachment 102832 [details]
First window

This is the first window to appear. Note the incorrect size (the window should
fit the desktop (as obtain when "Tiling Windows Horizontally" with only one
window visible))
(Reporter)

Comment 2

15 years ago
Created attachment 102833 [details]
Second Window

Second window to appear. Contains the page of the first selected article.

Comment 3

15 years ago
Nahor, are you still seeing this problem with a newer release (1.2.1 or 1.3a) of
Mozilla?
(Reporter)

Comment 4

15 years ago
Yes (trunk build 2003012404)

Comment 5

14 years ago
Nahor, is this still an issue with a current build?
(Reporter)

Comment 6

14 years ago
I haven't used Mozilla for a while, I use Firebird now.
It's still an issue in Firebird build 20031101.

I'll give it a try with Mozilla again and a more recent version of Firebird.
(Reporter)

Comment 7

14 years ago
Yep, still an issue with Mozilla 2003112508.

One thing changed however, the second window is now the correct size.

Also, I now have a multimonitor setup with one monitor in 1024x768 and the other
in 1280x1024. The first window is a bit bigger than my desktop, i.e. a bit over
2304 pixels wide. The normal size is 1280x1024 (minus the taskbar) to fit on my
primary monitor.
I don't know if this is new or not, I didn't have multiple monitors when I
opened this bug

Comment 8

14 years ago
Nahor, still seeing this in 1.6 or newer?

Seems like similar symptoms as bug 204752 or 230845.
Assignee: asa → general
QA Contact: asa → general
(Reporter)

Comment 9

14 years ago
(In reply to comment #8)
> Nahor, still seeing this in 1.6 or newer?
Still an issue with Firebird and Mozilla
  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040128
Firebird/0.8.0+)
  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040203)


> Seems like similar symptoms as bug 204752 or 230845.
It is similar to 230845 except that opening only one page works fine for me. I
have a problem only when I try to open a second link while the first isn't fully
loaded yet. I assume that either the author of bug 230845 is double-clicking
when single would be enough or that thunderbird is trying to open the link twice
for some reasons.
So bug 230845 can be marked as duplicate of this one.

As for bug 204752, I'm not sure it is the same problem. Mine triggers only when
Mozilla isn't already running. The other bug has Mozilla already running. Mine
was already present in 2002-10-14. The other says that it's new after 2003-04-30.
As for comment 204752#c3, it's bug 119131.

Comment 10

14 years ago
*** Bug 230845 has been marked as a duplicate of this bug. ***

Comment 11

14 years ago
->XP Apps
Assignee: general → jag
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps
Ever confirmed: true
QA Contact: general → pawyskoczka
Product: Core → Mozilla Application Suite

Comment 12

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 13

9 years ago
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 14

9 years ago
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 15

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.