Closed Bug 128712 Opened 22 years ago Closed 14 years ago

throbber disappears to 5 secs when starting to load another page when an alert is present

Categories

(SeaMonkey :: Themes, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bugzilla, Unassigned)

References

()

Details

turn on the "viewing a page with mix" SSL alert in the prefs.

Now open two windows:
in the first now go to https://telstra.com/tcoma/registration/join.asp
when you get the SSL alert leave it
Now switch to the second window and enter 
https://telstra.com/tcoma/registration/join.asp in the location bar and hit 
enter.

result: the throbber disappers for several seconds. I have no clue what mozilla 
is actually doing in the secs, it's not loading anything...

20020302

happens in both modern and classic
Product: Core → SeaMonkey
Assignee: hewitt → nobody
QA Contact: pmac → themes
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
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
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.