This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/urls.html Section: http://www.whatwg.org/specs/web-apps/current-work/#safe-passing-of-structured-data Comment: Should cloning properties preserve configurability, readonlyness, etc? Posted from: 2620:101:8003:200:6233:4bff:fe07:d951 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.2a1pre) Gecko/20110328 Firefox/4.2a1pre
In particular, the structured clone code says to create a property with the same name, but doesn't discuss any of the property flags. It also sounds like accessor properties will be turned into data properties whose value is the value returned by the getter, right?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: no spec change Rationale: The spec already mentions that property configurations are not preserved. Does it need to be made more explicit? I guess I can explicitly give the configuration of the new properties, would that be better? If so, what should it say, exactly? I am not familiar with this new configuration stuff.
mass-moved component to LC1