Re: [heycam/webidl] Propagate active script to callbacks (#902)

Yeah, I can understand that. Here is my proposal:

1. Land https://github.com/whatwg/html/pull/5722 (tracking active script/incumbent for promises correctly)
1. Land https://github.com/whatwg/html/pull/4571 on top of that (weak references, with proper active script/incumbent tracking)
1. Land this PR and its associated tests, in basically this form. (Tracking active script for Web IDL callbacks)
1. Investigate unification, i.e. no longer tracking active script and incumbent separately, but instead tracking incumbent execution context, and deriving active script from that.
    - This could involve tests like @hiroshige-g's above. Or even simplifications of incumbent to make it more like active script.

I will set aside my (local on-disk) unification pull request, so we can proceed incrementally. So at this point I think the ball is in other folks' courts. In particular, @syg is working on those HTML pull requests (and their 262 dependencies), and it would be good to get Mozilla or Apple input on the question posed by this PR and its associated tests about

```js
// sub/path/foo.js
setTimeout(eval, 0, 'import(`./example.mjs`)');
```

-- 
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/pull/902#issuecomment-662682701