311451 - Chrome XUL documents can't access script objects on the contentDocument for XUL IFRAMEs

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect)

Description

[Andrew Miller]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20051006 Firefox/1.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20051006 Firefox/1.4

In Firefox 1.5b1 and the nightlies, chrome XUL documents cannot access script
objects from another chrome document, for example iframe.contentDocument,
window.frames, or window.parent. Instead, they get a separate XPCOM wrapper that
does not share attributes.

Reproducible: Always

Steps to Reproduce:
1. Put test_context_bug.xul and test_context_bug_frame.xul into a chrome content
directory(file:/// or http:// won't show the bug).
2. Load test_context_bug.xul by a chrome URL
3. Observe the alerts that appear.
Actual Results:  
In affected browsers(Firefox 1.5b1 and a recent nightly build):
1. the iframeloaded alert pops up first, showing that the property was set
correctly.
2. the loaded alert pops up next.
3. the alert showing the results shows that the XULDocument from contentDocument
is actually an XPConnect wrapper, and the attribute which was previously set has
disappeared.

Expected Results:  
In step 3., the attribute should not have been undefined.

Comment 1

[Andrew Miller]

Attachment: test_context_bug_frame.xul

Comment 2

[Andrew Miller]

Attachment: test_context_bug.xul

Comment 3

[Martijn Wargers (dead)]

I can see this with:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060719 Minefield/3.0a1

Seems like a regression from bug 281988 to me (not sure, though).

Comment 4

[Boris Zbarsky [:bzbarsky]]

Actually, this is the expected behavior since the XPCNativeWrapper landing.  See http://developer.mozilla.org/en/docs/XPCNativeWrapper and in particular http://developer.mozilla.org/en/docs/XPCNativeWrapper#What_is_a_protected_script.3F