203355 - if main.js is editied on iPlanet webmail server without bringing server down, browser displays nothing.

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Matt Cowger]

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

Using iPlanet Messager Express 5.2.  Along with page, a 'main.js' file is sent
to the browser for various settings.  If this file is edited on the server while
server is up, any future accesses of the webmail page by a Mozilla browser will
cause the pages not to be rendered at all.  Note that this behavior does not
exist in other browsers such as a IE 4+ or Opera.

The page/code is being downloaded fine, as a View|Source shows the correct HTML,
its just that nothing is rendered on screen.  After bringing the server down,
then up, problem disappears.

Reproducible: Always

Steps to Reproduce:
1.  Modify main.js for iPlanet Messanger express
2.   Login to Messanger express with Mozilla.
3.

Actual Results:  
Page does not render (blank white page)

Expected Results:  
Page should render inbox screen.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Does the server actually send the main.js when Moz requests it?

Comment 2

[Matt Cowger]

The server reports sending the script file, though I haven't actually put a sniffer on to find out.  I would bet that it does send, however, because the behavior displayed by mozilla does not exist with other browsers, even when changing their UserAgent strings to match Mozilla's

Comment 3

[Wesha]

Sounds like some kind of mess in the cache; recently, I expierenced similar
problems with Mozilla still showing old pages after posting new topics to
phpBB-based forums. Cleaning cache always helps.

Reporter: would you please try cleaning Mozilla's cache after changing the file
in question? Does the problem persist after that?

Comment 4

[Matt Cowger]

This was our guess as well, but the problem persists even after clearing the Cache
and disbling the memory cache altogether.

Comment 5

[Matt Cowger]

I should also note that I have opened a report with Sun on this as well.

Comment 6

[Asa Dotzler [:asa]]

Matt Cowger, is this still a problem with Mozilla 1.6 or newer?

Comment 7

[Matt Cowger]

Asa,

I can't confirm or deny the bug any longer - I am no longer working at the
location where it was experienced, and as a result can't test it.

You could contact the current iPlanet systems admin at Bowdoin College
([e-mail]) for a confirmation.

Comment 8

[Brandon Hines]

I am experiencing what sounds to be the same issue.  When logging into iPlanet
mail server, I receive a few javascript errors and then the page comes up blank.
 This occurs with Mozilla 1.6, 1.7a on Linux and MacOS X.  I don't know about
Windows.

I do not have admin access to the iPlanet server, so I am only able to confirm
so much, but would be willing to assist in any other way possible.

Comment 9

[Asa Dotzler [:asa]]

Brandon, can you copy and paste the javascript errors to this bug? 

Comment 10

[Brandon Hines]

Here are the error messages:

Line 186
m[5] has no properties

Line 209
a has no properties

This occurs on the page after login.

Comment 11

[Gervase Markham [:gerv]]

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/

Comment 12

[Gervase Markham [:gerv]]

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.