Implementation-defined typeof still necessary?

[littledan]

Now that we have the HTML document.all object defined, including its typeof document.all = "undefined" behavior, do we still need to permit non-standard, non-callable exotic objects to have implementation-defined typeof, as defined in https://tc39.github.io/ecma262/#sec-typeof-operator-runtime-semantics-evaluation ? I'm not aware of any use cases for this in the Web; do other embedding environments need it?

See related discussion at whatwg/webidl#512 @annevk @TimothyGu

[bakkot]

Fun fact: old versions of I.E, up to I believe 8, return "unknown" for the typeof certain properties, but since those are already not attempting to conform to the latest version of the spec I don't think that's an issue. I don't think that behavior was carried over to Edge, though it's possible I'm mistaken.

[michaelficarra]

From IE10,

>> window.external.AddSearchProvider
undefined
>> window.external.IsSearchProviderInstalled
undefined
>> typeof window.external.AddSearchProvider
"unknown"
>> typeof window.external.IsSearchProviderInstalled
"unknown"
>> var x = window.external.AddSearchProvider
>> typeof x
"undefined"

[ljharb]

Both of those appear to be object in latest edge, whether direct or stored in a variable.

[littledan]

Let's phase out this phaseout strategy!

[TimothyGu]

Regardless of if Edge actually returns "unknown" anywhere, the infrastructure for returning "unknown" on typeof is certainly still there in ChakraCore: https://github.com/Microsoft/ChakraCore/blob/87249a17a484d54980c3823577acd66c2824eaa4/lib/Runtime/Types/RecyclableObject.cpp#L797-L800

It also has support for something called a "variant Date" that returns "date" when typeof is called on it, though I doubt it's used anywhere.

[littledan]

Interesting. It'd be great to hear from ChakraCore folks to understand if this behavior is important to them, cc @zenparsing.

[zenparsing]

I'm currently digging into this with respect to CC and will report what I find.