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: Wed, 26 Jan 2011 05:43:24 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PhyA8-0005gY-VY@jessica.w3.org>

--- Comment #4 from Boris Zbarsky <bzbarsky@mit.edu> 2011-01-26 05:43:24 UTC ---
Well, it's settable to null for the current page given existing spec text
(because it's replaceable, so writing to it shadows the property).

I suppose I could write a testcase that grabs the getter off the prototype
after setting to null and calls it on the window, etc... but I'm not sure
browsers' ES5 support is far enough along to make that sane.

So in the meantime, a simple way to tell apart replacement and assignment seems
to be navigation.

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 Wednesday, 26 January 2011 05:43:26 UTC

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