Closed Bug 276960 Opened 20 years ago Closed 19 years ago

Shift reload only reloads frameset but not frames referenced

Categories

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

1.0 Branch
x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ruediger.jungbeck, Unassigned)

Details

Attachments

(1 obsolete file)

If you have a frameset and all frames referenced unexpired in the disk cache,
shift reload only reloads the frameset (but not the frames).
Assignee: bugs → nobody
Component: Page Info → Layout: HTML Frames
Product: Firefox → Core
QA Contact: firefox.page-info → core.layout.html-frames
Did you use Firefox 1.0 for testing? It is somewhat confusing, since you
selected Version: 1.0 Branch. In the Product Core this would normally stand for
Mozilla 1.0 Branch *g*...
How did you see it only reloads the frameset (serverlog, packet-sniffer)?
I used Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107
Firefox/1.0

I used NETMON and can see the GET for the frameset (and FAVICON:ICO), but not
for the frames themselfes.
Reporter, do you have a testcase showing this problem?  If so, please post the
URL in this bug.
Attached file Wrong bug, sorry (obsolete) —
Comment on attachment 174813 [details]
Wrong bug, sorry

Sorry, attached to wrong bug.
Attachment #174813 - Attachment description: Tar file containing testcase as described → Wrong bug, sorry
Attachment #174813 - Attachment is obsolete: true
If you take http://www.rsj.de/frameset/default.asp you can see, that the lower
frame is not updated on every shift reload (it is updated on every second reload
only). This is not exactly the issue (because, than no reload worked), but for
the simple web based test case (just asp's), we needed at least some dynamic
content, and probably the cache attributes of the frameset or the other frame
have to do something with this.  
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/
The problem cannot reproduced in current versions (Firefox 1.0.6 or Firefox 1.5 B1)
Status: UNCONFIRMED → RESOLVED
Closed: 19 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.

Attachment

General

Creator:
Created:
Updated:
Size: