Closed
Bug 613459
Opened 14 years ago
Closed 14 years ago
Firefox 4 Beta 7: Node.prototype is undefined when accessed in crossdomain environment.
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 616992
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | betaN+ |
People
(Reporter: fake_healer, Assigned: mrbkap)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.200 Safari/534.10
Build Identifier: 4.0b7
I have an iframe which is in a subdomain. When I try to extend the Node.prototype in it, it says it's undefined.
The "real" test contains proper loading functionality to ensure the frame is loaded:
http://fimbul.com/xc/xdomain.html
A more thourough test:
http://fimbul.com/xc/ff4_xdomain.html
This bug started to occur in Beta 7. In Beta 6 this worked fine.
Reproducible: Always
Steps to Reproduce:
1. Create a html:
<html>
<head>
<script>
document.domain = "domain.com";
window.onload = function() {
alert(window.frames["frm"].Node.prototype);
}
</script>
</head>
<body>
<iframe id="frm" name="frm" src="http://sub.domain.com/xdomainframe.html"></iframe>
</body>
</html>
2. Create xdomainframe.html:
<html>
<head>
<script>
document.domain = "domain.com";
</script>
</head>
<body></body>
</html>
3. Add the domain.com and sub.domain.com to the hosts file:
127.0.0.1 domain.com
127.0.0.1 sub.domain.com
4. Run the test in Firefox 4 Beta 7: http://domain.com/xdomain.html
Actual Results:
The alert shows 'undefined'.
Expected Results:
The alert should show '[object DOM Constructor.prototype]'.
As mentioned above, the code works in Firefox versions up to Beta 7.
Component: General → JavaScript Engine
Product: Firefox → Core
|
||
Updated•14 years ago
|
Assignee: nobody → general
QA Contact: general → general
|
||
Comment 1•14 years ago
|
||
Looks like a cross-compartment wrappers regression?
Assignee: general → nobody
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Component: JavaScript Engine → XPConnect
Ever confirmed: true
QA Contact: general → xpconnect
|
||
Comment 2•14 years ago
|
||
Yup, sure does. Over to mrbkap.
Assignee: nobody → mrbkap
blocking2.0: ? → beta9+
|
Assignee | |
Comment 3•14 years ago
|
||
This is probably a dupe of bug 616992.
|
|
||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
As per today's meeting, beta 9 will be a time-based release. Marking these all betaN+. Please move it back to beta9+ if you believe it MUST be in the next beta (ie: trunk is in an unshippable state without this)
blocking2.0: beta9+ → betaN+
No longer depends on: 616992
You need to log in
before you can comment on or make changes to this bug.
Description
•