Open
Bug 486067
Opened 16 years ago
Updated 3 years ago
setting window.opener to null does not hide MessageEvent.origin
Categories
(Core :: DOM: Events, defect, P5)
Core
DOM: Events
Tracking
()
UNCONFIRMED
People
(Reporter: sephr, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
|
821 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.8) Gecko/2009032712 Ubuntu/8.10 (intrepid) Firefox/3.0.8 GTB5
Build Identifier:
If you create a window and set it's opener to null, MessageEvent's origin still contains the opening window's protocol and host.
Reproducible: Always
Steps to Reproduce:
1. var win = window.open();
2. win.opener = null;
3. win.location.replace("a data uri that tries to get MessageEvent.origin")
Actual Results:
MessageEvent.origin is the window's opener's protocol and host.
Expected Results:
MessageEvent.origin is not the window's opener's protocol and host.
| Reporter | ||
Comment 1•16 years ago
|
||
| Reporter | ||
Updated•16 years ago
|
| Reporter | ||
Comment 2•16 years ago
|
||
I didn't notice the last testcase triggered the pop-up blocker. This one doesn't.
Attachment #370145 -
Attachment is obsolete: true
| Reporter | ||
Comment 3•16 years ago
|
||
I just tested the testcase on WebKit and WebKit's solution is to set MessageEvent.origin null.
Comment 4•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•