Bug 7170 – `window.parent.[frameName].location=' fails if the target frame has not yet loaded a document

• Component: Frames
• Status: CLOSED FIXED

[rahul abrol]

(N.B. this is similar to bug #6281)

a safari user created a test site containing three frames, where one frame (main.htm) sets the location of the two other frames through javascript (e.g. window.parent.frame1.location=...).  apparently safari is the only browser that (occasionally?) fails to display the content in these two frames.  the full discussion is located here:

http://discussions.apple.com/thread.jspa?threadID=337792

i'm guessing this is due to security restrictions, but i've verified that firefox 1.5.0.1, camino 1.0rc1, and opera 9.0pre2 all allow this cross-frame javascript code.  both the latest safari stable and ToT fail.

i'm attaching a slightly reduced test-case of the problem.

[rahul abrol]

Created attachment 6377 [details]
testcase (start.tgz)

the attached archive contains four files.  open start.html.

the top frame (banner.htm) remains empty in safari (no js errors either), whereas other browsers seem to have no problems here.

[Geoffrey Garen]

Created attachment 6390 [details]
reduction.zip

Attached a more reduced reduction (reduction.zip).

[Geoffrey Garen]

The reduction will pass in Safari if and only if:
(1) The target frame loads an initial document (even an empty document).
(2) The target frame loads prior to the frame that tries to set its src value.

[Alexey Proskuryakov]

See also: bug 7161.

[Joost de Valk (AlthA)]

Good testcase. Confirmed.

Looks like this was fixed in r17144.

[Alexey Proskuryakov]

I added a layout test (committed r18278), because this bug got fixed "magically",