269892 - frames don't always reload correctly when using scripts

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Chris Fritsch]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0

The intranet of my university uses Hyperwave, which basically has a small frame
showing the tree structure of the content and a big frame showing the actual
content. When I click on an item of the tree structure, the big frame loads the
correct new content. However, the tree frame itself doesn't open the clicked
branch, it just makes nothing. The operation itself involves a lot of scripting
(tested with IE6, all scripts had to ask for permission). This renders the whole
intranet to useless, as the first page displayed in the tree frame is
'Loading...' and not updating correctly (correctly = not at all, thus giving no
further access). This can be bypassed, however, if I right-click on the frame
and then choose to reload it manually. Then it updates to its correct (new)
state. As most of my friends (non CS students) migrate to Firefox now, this is
quite a proplem ('better future? right now it does not even work').



Reproducible: Always
Steps to Reproduce:
1. get a login to intranet.fh-ingolstadt.de (University of Applied Science,
Ingolstadt, Germany)
2. log in
3. see that u can not access anything without manually reloading the 'table of
content' frame.
4. Manually reload it

Actual Results:  
After that, it worked. But end-users might not have the knowledge to bypass it.

Expected Results:  
Worked? (Loading the content frame correctly automatically)

Used a standard install of Firefox 1.0

Comment 1

[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 2

[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.