881677 - Wrong value decompilation in indirect proxies error messages

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Till Schneidereit [:till]]

STR:
execute the following code in the shell:
Proxy.create({})[0];

Actual result:
"TypeError: Proxy.create(...) is not a function"

Expected result:
At the very least, "TypeError: 0 is not a function" or similar. It looks like we're decompiling the value preceding the one we should.

Ideally, though, the error would say what's actually going on: the proxy didn't define a [[Get]] trap, so all [[Get]]s fail.


This might not be too important, given that we want to retire the indirect proxies API at some point. OTOH, that point might be somewhat far off, because web.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Is this basically the same as bug 862852?

Comment 2

[André Bargull [:anba]]

Proxy.create was removed in bug 892903.