| 12:49 | <Ms2ger> | annevk: my head hurts as usual when I think about questions like this, so I'll pass it to you: if I queue a task, do I have a "current realm" when the steps run? |
| 12:50 | <Ms2ger> | (Or anyone else who knows) |
| 12:50 | <Shannon Booth> | you do not! |
| 12:51 | <Shannon Booth> | (its kind of not really defined in the spec, and an execution context needs to be pushed as a workaround) |
| 12:51 | <Ms2ger> | Okay, I was right to be paranoid, then :) |
| 12:51 | <Shannon Booth> | i think every implementation must have their own solution for it |
| 12:51 | <Ms2ger> | (Is it paranoia if they're really out to get you?) |
| 13:28 | <annevk> | Maybe there should be an issue? Not entirely sure when this comes up. Usually I put the global in a variable before going in parallel and reuse that global for the task. With queue a global task you could conceivably have a current global. (Remember, don't use "queue a task".) |
| 15:04 | <Shannon Booth> | it is quite common since it also impacts cases a promise is reacted within a task as there is nothing on incumbent stack for the job callback, so prepare to run a callback may also be needed. I’ve sort of lumped this under https://github.com/whatwg/html/issues/4342 and https://github.com/whatwg/webidl/issues/135#issuecomment-772716243 when looking at it before, but maybe is it different |
| 15:05 | <annevk> | That first one looks on point for sure. |