Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unenumerable supported property names are badly defined #79

Closed
nox opened this issue Dec 22, 2015 · 2 comments
Closed

Unenumerable supported property names are badly defined #79

nox opened this issue Dec 22, 2015 · 2 comments
Labels
☕☕ difficulty:medium Hard to fix ⌛⌛ duration:medium Shouldn't be too long to fix editorial Changes that do not affect how the standard is understood.

Comments

@nox
Copy link
Member

nox commented Dec 22, 2015

It is not clear whether they should appear in the result of Object.getOwnPropertyNames. It should probably be clearly stated that they are to.

Cc @heycam

@annevk
Copy link
Member

annevk commented Feb 16, 2016

Well, we should define this by defining PlatformObjectOwnPropertyKeys, as part of ES6 integration.

@tobie tobie added ⌛⌛ duration:medium Shouldn't be too long to fix editorial Changes that do not affect how the standard is understood. ☕☕ difficulty:medium Hard to fix labels Jun 19, 2016
@annevk
Copy link
Member

annevk commented Aug 10, 2017

Closing as duplicate of a more active issue: #400.

@annevk annevk closed this as completed Aug 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
☕☕ difficulty:medium Hard to fix ⌛⌛ duration:medium Shouldn't be too long to fix editorial Changes that do not affect how the standard is understood.
Development

No branches or pull requests

3 participants