Fails to complete opening of the page - displays an egg timer on screen

RESOLVED EXPIRED

Status

SeaMonkey
General
--
minor
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: Nicholas Warwick, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208

Whilst opening the page
https://securetrak.checkpoint.com/eservice_enu/start.swe?SWECmd=GotoView&SWEView=Home+Page+View+(eService)
the browser hangs with an egg timer displayed despite the "done" being displayed
in the left hand corner. Reviewing the source shows this to be an xml page the
top portions as below:-

<?xml version="1.0" encoding="UTF-8"?>
<APPLICATION NAME="Siebel eService">
<USER_AGENT MARKUP="XML"/>
<NAVIGATION_ELEMENTS>
<TOOL_BAR NAME="SWEToolBarForm6" PATH="/eservice_enu/start.swe">
</TOOL_BAR>
<SCREEN_BAR>
<SCREEN_TAB NAME="Service Request Screen (eService)" CAPTION="SecureTrak
Service" ACTIVE="TRUE">
<ANCHOR TARGET="_sweview" PATH="/eservice_enu/start.swe">
<CMD VALUE="GotoPageTab" NAME="SWECmd">
<ARG NAME="SWENeedContext">

Obviously I do not know if this is a problem with Checkpoint's coding of the
site or a problem with Mozilla.

Reproducible: Always

Steps to Reproduce:
1.Browse to https://usercenter.checkpoint.com
2.Logon
3.Open Services and Downloads
4.Open SecureTrak
5.Open view Service Requests
Actual Results:  
The browser hung with an egg timer displayed. This meant I was an unable to open
any of the links on the page.

Expected Results:  
Completed opening the page so I could open a link on the page.

This works on IE 6 and Opera 7.10. I appreciate that you will not be able to
recreate this without a valid Checkpoint support logon but as Mozilla is widely
used by the security community I felt it was worth mentioning.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.