- From: Timothy Gu <notifications@github.com>
- Date: Mon, 07 Aug 2017 04:10:21 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 7 August 2017 11:10:44 UTC
TimothyGu commented on this pull request. > @@ -12014,19 +12014,26 @@ However, for [=legacy platform objects=], properties on the object must be enumerated in the following order: -1. If the object [=support indexed properties|supports indexed properties=], then - the object’s [=supported property indices=] are - enumerated first, in numerical order. -1. If the object [=support named properties|supports named properties=] and doesn't implement an [=interface=] with the - [{{LegacyUnenumerableNamedProperties}}] Yes, `LegacyUnenumerableNamedProperties` controls the `enumerable` bit in the descriptor but not the existence of the key. See [[GetOwnProperty]]. The original pseudo-algorithm defines the "enumeration order", basically the order of for-in loops, which accounts for both enumerability and key existence. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/pull/402#discussion_r131628540
Received on Monday, 7 August 2017 11:10:44 UTC