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.

Sign up for GitHub

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

Jump to bottom

Investigate moving Object.isSealed, isFrozen, and isExtensible to the shim #232

Open
ljharb opened this issue May 6, 2014 · 2 comments
Open

Investigate moving Object.isSealed, isFrozen, and isExtensible to the shim #232

ljharb opened this issue May 6, 2014 · 2 comments
Labels
ES5 sham
Milestone
v4.1.0

Comments

@ljharb
Copy link
Member

ljharb commented May 6, 2014

Should we move the following methods to the shim, out of the sham?

  • Object.isSealed
  • Object.isFrozen
  • Object.isExtensible
@ljharb ljharb added the ES5 sham label May 6, 2014
@ljharb ljharb added this to the v3.1.0 milestone May 6, 2014
@ljharb ljharb modified the milestones: v4.0.0, v4.1.0 Aug 14, 2014
@ExE-Boss
Copy link

ExE-Boss commented Oct 4, 2019

We could probably move Object.isExtensible(…), as it’s spec compliant, but the others will always return false when polyfilled, so ¯\_(ツ)_/¯.

@ljharb
Copy link
Member Author

ljharb commented Oct 4, 2019

Given that when polyfilled, nothing can possibly be sealed or have extensions prevented, that's actually correct behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ES5 sham
Projects
None yet
Milestone
v4.1.0
Development

No branches or pull requests
2 participants
@ljharb @ExE-Boss