-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Normative: Remove implementation-defined typeof behavior #1441
Conversation
Pretty hard to test a lack of unknown implementation-defined behavior here, so I don't think this would need any tests :-) |
I'm wondering about the "needs consensus" label here. Do you think this needs to be presented at a TC39 meeting, or could we get consensus for it on GitHub? |
Generally, every normative change requires committee approval; it certainly seems like something we could decide on GitHub, but I would be uncomfortable merging a non-bugfix normative change without that explicit consensus. |
Just wanted to remind that @@toStringTag, unlike Otherwise, I like the change this issue is proposing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should also remove the note below the table as it's no longer applicable.
20fee9e
to
017ca29
Compare
It’s always preferred when committee members can drive their own needs-consensus changes. |
Alright, thanks for the clarification and quick review. |
So what should happen when a needs-consensus change doesn't 'belong' to a committee member? |
@jmdyck in that case (or when no committee member is driving it) it's up to the editors to proactively add it to the agenda, as time permits. |
Cool, thanks. |
The HTML change for this seems to have landed whatwg/webidl#640 |
To be clear, that text can be removed if this lands. It's mostly added there since this change is taking a while. |
Previously, the ECMAScript specification permitted non-callable non-standard exotic objects to have implementation-defined typeof, within certain limits. Although some ECMAScript implementations may have taken advantage of this possibility historically, it's not clear that anyone needs it anymore. Instead, other mechanisms can be used by embedders to indicate aspects of objects. Closes tc39#1440
See tc39/ecma262#1441. This therefore reverts 5de45d9.
See tc39/ecma262#1441. This therefore reverts 5de45d9.
Previously, the ECMAScript specification permitted non-callable
non-standard exotic objects to have implementation-defined typeof,
within certain limits. Although some ECMAScript implementations
may have taken advantage of this possibility historically, it's not
clear that anyone needs it anymore. Instead, other mechanisms can
be used by embedders to indicate aspects of objects.
Closes #1440