-
Notifications
You must be signed in to change notification settings - Fork 165
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
typeof operator and platform objects #512
Comments
Sort of. HTMLAllCollection needs to return "undefined". Which the ES spec doesn't allow, of course. |
But yes, for the rest we should spec that they return "object" |
Now it does :) See https://tc39.github.io/ecma262/#sec-IsHTMLDDA-internal-slot-typeof and whatwg/html#3087. |
Oh, a COMEFROM spec. Lovely. ;) |
I actually think ES shouldn't say this is implementation-defined. It should be host-defined and there should be a hook for hosts to make it work more automatically. And perhaps given that |
Good point; I filed tc39/ecma262#1440 to discuss a simplification here. |
The
typeof
operator is defined for "Object (non-standard exotic and does not implement [[Call]])" to return "Implementation-defined. Must not be "undefined", "boolean", "function", "number", "symbol", or "string"."From
it seems that "non-standard" means "non-ECMA-262". Then named property objects, legacy platform objects, etc. are all non-standard. We should say in Web IDL that they should all return "object"
The text was updated successfully, but these errors were encountered: