Re: Removing writable [Replaceable] properties

2012-12-21 Thread Boris Zbarsky
On 12/20/12 12:14 PM, Jeff Walden wrote: WebKit gives the old behavior, but only for some of the listed properties -- it doesn't for status or name. OK. Given that, I think we should just go ahead and make these non-replaceable. Given WebKit doesn't make "status" and "name" replaceable, th

Re: Removing writable [Replaceable] properties

2012-12-20 Thread Jeff Walden
On 12/20/2012 03:38 PM, Boris Zbarsky wrote: > On 12/20/12 12:14 PM, Jeff Walden wrote: >> Setting it creates a shadowing property on window itself, using the exact >> value passed in. >> >>// Current Gecko >>alert(typeof window.screenX); // number >>window.screenX = "123"; >>aler

Re: Removing writable [Replaceable] properties

2012-12-20 Thread Robert O'Callahan
Seems like a reasonable change to me, for the inner*, outer* and screen* properties. I don't know about the others. Rob -- Jesus called them together and said, “You know that the rulers of the Gentiles lord it over them, and their high officials exercise authority over them. Not so with you. Inst

Re: Removing writable [Replaceable] properties

2012-12-20 Thread Boris Zbarsky
On 12/20/12 12:14 PM, Jeff Walden wrote: Setting it creates a shadowing property on window itself, using the exact value passed in. // Current Gecko alert(typeof window.screenX); // number window.screenX = "123"; alert(typeof window.screenX); // string, not number Er... no. If

Removing writable [Replaceable] properties

2012-12-20 Thread Jeff Walden
Gecko (not specs) has a concept of writable [Replaceable] attributes. It uses them for these properties: window.innerWidth window.innerHeight window.outerWidth window.outerHeight window.screenX window.screenY window.opener window.status window.name In our implementation, a wri