W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11839] window.opener needs to be writable, not readonly (as it is in Gecko, Chrome, IE)

From: <bugzilla@jessica.w3.org>
Date: Sun, 23 Jan 2011 02:37:43 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pgppn-0001g1-3G@jessica.w3.org>

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
            Summary|window.opener needs to be   |window.opener needs to be
                   |writable, not readonly      |writable, not readonly (as
                   |                            |it is in Gecko, Chrome, IE)

--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> 2011-01-23 02:37:42 UTC ---
Er, that test doesn't test what I want to test.  This one does:

file1.html: <div onclick="window.open('file2.html')">click me</div>

file2.html: <script>
              window.opener = null;
              window.location.href = "file3";

file3.html: <script>alert(window.opener);</script>

This alerts "[object DOMWindow]" twice in Safari, "[object DOMWindow]" and then
"null" in Chrome, "[object Window]" and then "null" in Gecko, "[object Window]"
twice in Opera, "[object]" and "null" in IE.

So it looks like the property is just replaceable in Opera and Safari, but is
both replaceable _and_ writable in Gecko, IE, and Chrome.

Cameron is cced because once this property is writable WebIDL needs to define
what it means for a property to be both writable _and_ replaceable.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 23 January 2011 02:37:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:38 UTC