Closed Bug 188403 Opened 22 years ago Closed 22 years ago

frames not always loaded correctly (something to do with caching?)

Categories

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

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: zilla, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030109 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030109 After installing a new nightly build, certain pages which used framesets stopped loading correctly. Specifically, the first time I load a frameset only one frame is rendered, the others remaining as completely blank areas of the window. On subsequent loads, however, further frames sometimes appear, up to the whole page being displayed correctly. At first, I had problems reproducing this bug reliably, and many of the test cases I produced failed to exhibit the same behaviour. However, it seems to be related in some way to the cached status of the subframes, as I can reliably get a single-frame behaviour if I clear my cache. The only related bug I found is bug 18297, but the current explanation for that involves Java and/or JavaScript, whereas I have successfully reproduced this with pages that use neither. I have not provided a testcase other than the URL, as it has proved difficult to produce one, but the source of the frameset at the URL provides a fairly clear case. Reproducible: Always Steps to Reproduce: 1.Clear the browser's cache using the preferences window [if the page has already been visited] 2.Go to http://www.the-cutting-edge.demon.co.uk/o/index.html (or any page that uses a similar arrangement of frames) Actual Results: Only the top-left frame loaded, the rest of the page remaining white. Expected Results: Four frames should load, filling the entire window.
worksforme, on that url, linux 2003-01-09-08 trunk nightly.
OK, it seems I've been a fool, and this isn't a bug in mozilla at all, but an odd firewall problem which happened to crop up at the same time as installing the new build. Sorry for wasting anyone's time - including mine, although it gave me an excuse to look into a couple of things...
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
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.