182052 - first hit of the pkware web site results in a blank page

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Wenqing Jiang]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021126

go to the web site, the page is blank.
hit reload, the page shows up.
To reproduce the problem, clear mem/disk cache and visit the URL again.

Reproducible: Always

Steps to Reproduce:
1.go to the web site, the page is blank.
2.hit reload, the page shows up.
3.To reproduce the problem, clear mem/disk cache and visit the URL again.

Actual Results:  
The page is blank at first visit.

Expected Results:  
The page should show up normally at first visit.

Comment 1

[Michael Lefevre]

strange... I can't reproduce this - using trunk 2002112607, win2000.

Wenqing - are you using any kind of proxy? do you hava javascript disabled?

Comment 2

[Wenqing Jiang]

I'm not using any proxy, and javascript is enabled for browser.
I'll use another computre to try this out tonight.

right-click then "view page source" will display the html of
the blank page, and after reload the page source seems the
same.  The means for the first hit the source is retrieved
from the web site but somehow not rendered.

I will post more info when tested on other machines.

Comment 3

[Frederic Bezies]

Seeing the same behaviour :-/

Very strange.

Site is calling a js called browser.js, which seems to detect only IE browser
and if no IE is found, it loads a NS 4.x CSS. Maybe this is related ?!

Using 2 hours old CVS based build - WinXP-SP1.

Comment 4

[Wenqing Jiang]

I used another machine with mozilla of a week old, also running on win2k,
and reproduced the problem.

The problem can be repeated if you visit another URL, then clean the mem
and disk cache, and revisit the pkware web site.  IE 6 seems not vulnerable
to it.

I removed the old mozilla and put in 2002112607, (just download and
extract mozilla-win32.zip), and the problem is intact.  I'm not sure if
the preference setting can cause that problem.  JavaScript is enabled
for the browser during the test.  What else settings should I report,
if the problem can't be reproduced by testers in Mozilla Org?

Comment 5

[Michael Lefevre]

ok, I tried it again, this time with just window and no other tabs - cleared the
mem and disk cache, then went to the site, and got the blank page. confirming
this so it doesn't get lost, but it needs more figuring out... not sure how though.

Comment 6

[Wenqing Jiang]

the bug is still alive in build 20030114.

Comment 7

[Wenqing Jiang]

Miraculously, the problem is gone for build 2003011608.  You
can check what's going on after build 20030114, but I think
this bug can be marked as fixed and resolved.

Isn't it surprising?

Comment 8

[Wenqing Jiang]

The bug surprised me again by returning to build 2003011804.

Comment 9

[Daniel Wang]

reporter (Wenqing Jiang), does this bug occur if you save the site
page (Web page, complete option) and load it locally?

Comment 10

[Wenqing Jiang]

Sorry I can't reproduce the bug now.  It's quite elusive.  Just close
the bug and I'll reopen it if it appears again.

Comment 11

[Daniel Wang]

resolve as wfm per reporter comment