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

Fix Object.getOwnPropertyNames(window) replacement #181

Merged
merged 1 commit into from
Mar 17, 2016
Merged

Fix Object.getOwnPropertyNames(window) replacement #181

merged 1 commit into from
Mar 17, 2016

Conversation

Macil
Copy link
Contributor

@Macil Macil commented Mar 17, 2016

There's an issue that would cause Object.getOwnPropertyNames(window) to return outdated results in some browsers. It would try to call the native Object.getOwnPropertyNames and then fall back, but there was a mistake in the try block so it would always fall back.

(This caused some really fun issues when mixing Babel code where some used the transform-runtime plugin and some didn't. Before I realized the cause of it was so simple, I started documenting this example because I imagined the fix would be much more involved.)

In affected browsers, this would cause
Object.getOwnPropertyNames(window) to return outdated results.
@zloirock
Copy link
Owner

Thanks, looks like a bug after splitting internal modules in 2.1.

zloirock added a commit that referenced this pull request Mar 17, 2016
Fix Object.getOwnPropertyNames(window) replacement
@zloirock zloirock merged commit 9d4c0f9 into zloirock:master Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants