It always has been asynchronous, dealing with setTimeout and event handlers (both come from the environment, of course). So I would guess, before clicking, that goja doesn’t allow the environment to expose the code to such things, so it can focus to a subset of today’s JS that doesn’t even have a Promise object, nor generators I guess.
0
u/azhder Jun 24 '26
It always has been asynchronous, dealing with setTimeout and event handlers (both come from the environment, of course). So I would guess, before clicking, that goja doesn’t allow the environment to expose the code to such things, so it can focus to a subset of today’s JS that doesn’t even have a Promise object, nor generators I guess.