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

I'm starting to come around to @littledan's point of view, that while this is the correct thing to do, but is not worth the implementation effort.

> does it affect any cases besides when eval (or possibly other kinds of functions implemented by the platform which parse JavaScript) is used directly as a WebIDL callback?

It affects any case where the platform function is dependent on the active script. I think in practice that's only going to be things like `eval` and `setTimeout`, because the only thing that currently depends on the active script is `import()` path resolution, and the only thing that triggers `import()` is author code.

We may want to remove active script tracking from job callbacks as well, since @hiroshige-g is discovering that no browsers seem to do that either?

-- 
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-908730529