Closed Bug 139192 Opened 24 years ago Closed 24 years ago

Page will not load in rc 1 (2002041711)

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

x86
Windows NT
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dkerber, Assigned: john)

References

()

Details

Similar to some other 'page won't load' descriptions. Mozilla rc 1 will not load this url at all on my work system. Loads fine from home, with same OS (NT4, SP6a). NS6 will load just the top frame; Mozilla rc1 will load nothing. NS 4.7x works fine. Says download complete after about 0.5 seconds, then nothing shows. Seti@home (setiathome.ssl.berkeley.edu) personal stats page gives "Cgi error: command not recognized."
WFM with Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.0rc1) Gecko/20020417
Problem appears to be with the site's javascript. If I turn off javascript support in rc1, it loads ok. Sorry for the false alarm. The problem (CGI error) with seti@home's individual stats page still occurs, however.
David: turning of JS shouldn't be a solution to see a website. at least it works for me with 1.0RC1 on Linux.
I agree, but if the js is bad, and is required to load the page, then there's not much else I can do to see the page other than disable the js. I e-mailed the webmaster about the problem and he's looking at it. Has anybody else tried it on NT? Maybe the problem isn't the js itself, but NT's interpretation of the quotes, etc?
reporter (David): platform shouldn't make any difference to mozilla's interpretation of the script. Page works fine for me (1.0, win2k). Can you reproduce this problem with a clean install of a recent version of mozilla (e.g. 1.0) (but with JS enabled)? if you can, please comment again. if not, please resolve this bug as WORKSFORME. thanks very much.
Marking WFM, from the above comments.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.