Re: Global lexical tier

2015-09-02 Thread Andreas Rossberg
On 3 September 2015 at 01:58, Brendan Eich wrote: > I was there, I just re-read and re-remembered. I do not agree with Allen > that some tiny needle was uniquely threaded. Rather, an aesthetic > preference for the new ES6 binding forms to have a lexical contour of their >

Re: Global lexical tier

2015-09-02 Thread Brendan Eich
saam barati wrote: Thanks. Reading now. I'm clearly bad at email :/ Naw, this stuff is always harder to find than it should be. I was there, I just re-read and re-remembered. I do not agree with Allen that some tiny needle was uniquely threaded. Rather, an aesthetic preference for the new

Re: Global lexical tier

2015-09-02 Thread Brendan Eich
Andreas Rossberg wrote: On 3 September 2015 at 01:58, Brendan Eich > wrote: I was there, I just re-read and re-remembered. I do not agree with Allen that some tiny needle was uniquely threaded. Rather, an aesthetic preference for the

Re: Property ordering of [[Enumerate]] / getOwnPropertyNames()

2015-09-02 Thread Allen Wirfs-Brock
On Sep 2, 2015, at 4:10 PM, John-David Dalton wrote: > Hiya, > > > [Enumerate]] must obtain the own property keys of the target object as if > > by calling its [[OwnPropertyKeys]] internal method > > Whoa that's tricky language. I assumed reading it that [[Enumerable]] was to > follow the

Re: Re: Property ordering of [[Enumerate]] / getOwnPropertyNames()

2015-09-02 Thread Scott Sauyet
John-David Dalton wrote: > It's odd to me that: > > Reflect.ownKeys() has defined order but > Reflect.enumerate() doesn't > > I'm using Reflect.enumerate() to create a `keysIn` implementation (like > `keys` but for own & inherited key > names). > > :+1: for more

Re: Global lexical tier

2015-09-02 Thread Allen Wirfs-Brock
On Sep 2, 2015, at 4:58 PM, Brendan Eich wrote: > saam barati wrote: >> Thanks. Reading now. >> >> I'm clearly bad at email :/ > > Naw, this stuff is always harder to find than it should be. > > I was there, I just re-read and re-remembered. I do not agree with Allen that > some tiny needle

Re: Re: Property ordering of [[Enumerate]] / getOwnPropertyNames()

2015-09-02 Thread John-David Dalton
Hiya, > [Enumerate]] must obtain the own property keys of the target object as if by calling its [[OwnPropertyKeys]] internal method Whoa that's tricky language. I assumed reading it that [[Enumerable]] was to follow the order of [[OwnPropertyKeys]] (as part of "as if by") and walking the

Re: Finding elements that are hidden due to overflow: hidden

2015-09-02 Thread Tab Atkins Jr.
On Tue, Aug 25, 2015 at 6:39 PM, Behrang Saeedzadeh wrote: > Looks like at the moment DOM does not expose any properties that signify > whether an element has become hidden due to an overflow: hidden on their > parent element. > > Any chance of adding this feature to DOM?