Re: [whatwg] Unforgeable document property

On Fri, 23 Sep 2011, David Bruant wrote:
>
> [with correct public-script-coord address]
> 
> Le 23/09/2011 11:54, David Bruant a écrit :
> > Hi,
> > 
> > I have noticed on a recent commit [1] that the "document" property of the
> > window object is now defined as [[Unforgeable]] (and still readonly). As per
> > WebIDL, it makes the property non-configurable (in ECMAScript 5 terms).
> > Consequently, it will make impossible to wrap the object document with an
> > ES.next proxy [2] and replace the "document" property value with the wrapped
> > document.
> > 
> > I think that there is definitely a use case here as replacing the document
> > with a proxy could help developers fixing the DOM and adding workarounds to
> > browser bugs. Consequently, I think the "document" property of the window
> > object should be kept configurable.

Is this compatible with the Web?

The change was made to align the spec with implementations.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'