Closed Bug 341679 Opened 20 years ago Closed 20 years ago

Error when a frameset built by JS refers to the creator file

Categories

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

x86
All
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: pallosp, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2 Isolated error: left.html: anything right.html: <html> <head> <script language="javascript"> if (window==top) { document.write('<frameset cols="35%,*">'); document.write(' <frame src="left.html">'); document.write(' <frame src="right.html">'); document.write('</frameset>'); } </script> </head> <body> right </body> </html> Reproducible: Always Steps to Reproduce: Open right.html Actual Results: Two frames appear and the right-hand side frame remains empty. Expected Results: It should display the text "right".
It is a browser caching problem. At http://enciklopedia.fazekas.hu/ I worked around it by concatenating a unique query string to the url of the empty frame, so from now on the site won't reproduce the problem.
this is from bug 228829, and seems to be what that bug intended.
Assignee: general → nobody
Component: General → Layout: HTML Frames
OS: Windows XP → All
Product: Mozilla Application Suite → Core
QA Contact: general → layout.html-frames
Version: unspecified → Trunk
Attached file testcase
with current trunk, the content window is empty.
Yep. Our behavior is identical to that of IE and Opera, and is the behavior we want here.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Could you explain why it is the expected behavior? I'd like if the code worked in the following way: 1. right.html is loaded 2. It is the top window, so it creates the frameset 3. In the created frameset right.html is not the top window, so the content of right.html is loaded. There is no infinite recursion. How can the detailed behavior be reached? Did I do something wrong?
> There is no infinite recursion. But telling this in the browser code is impossible (equivalent to solving the halting problem). > How can the detailed behavior be reached? Use a separate page for the frame?
And it's the expected behavior because it's what most modern UAs do.
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: