This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5909 - Need a solution for replaceable properties
Summary: Need a solution for replaceable properties
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P4 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2008-07-29 21:55 UTC by Ian 'Hixie' Hickson
Modified: 2010-10-04 14:46 UTC (History)
4 users (show)

See Also:


Description Ian 'Hixie' Hickson 2008-07-29 21:55:09 UTC
window.opener and some other properties can be replaced -- they are readonly, but setting them blows away the original attribute and its semantics.

Currently this is pending on WebIDL introducing [Replaceable] or some such.
Comment 1 Cameron McCormack 2008-11-24 04:46:23 UTC
[Replaceable] is now in Web IDL:

This doesn't make the property deletable, though.  Should it?

Comment 2 Ian 'Hixie' Hickson 2008-12-30 00:58:52 UTC
I've marked .opener. I need to do more research to determine what else needs to be so marked, but I'll do that separately.
Comment 3 Ian 'Hixie' Hickson 2009-01-14 08:48:02 UTC
This would be something easy for someone to run with if they wanted something simple to get involved.
Comment 4 Maciej Stachowiak 2010-03-14 13:15:16 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.