Re: [heycam/webidl] "platform object" for ECMAScript vs. IDL values (#680)

The main thing I'm worried about is grabbing state from the object that should perhaps have been inaccessible to the caller. E.g., specifications cannot mutate the JavaScript object without bridging, and JavaScript cannot access private state without bridging.

This might also be more relevant when there's not necessarily a JavaScript side for an object and it's WebAssembly or some such? (Haven't thought too much about that though.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/680#issuecomment-471453613

Received on Monday, 11 March 2019 08:53:31 UTC