You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rename emscripten_main_browser_thread_id to emscripten_main_runtime_thread_id. NFC (#18872)
The better reflects that is actually being returned here. In fact,
there may be no main browser thread at all, and we have never tracked
the thread ID of the main browser thread, only the main runtime
thread.
Use a macro to continue to support the old name, but mark is as
deprecated so folks will get a warning.
Also, update the corresponding
EM_CALLBACK_THREAD_CONTEXT_MAIN_BROWSER_THREAD macro.
case{{{cDefine('EM_CALLBACK_THREAD_CONTEXT_MAIN_BROWSER_THREAD')}}}: return0;// The event callback for the current event should be called on the main browser thread. (0 == don't proxy)
205
+
case{{{cDefine('EM_CALLBACK_THREAD_CONTEXT_MAIN_RUNTIME_THREAD')}}}: return0;// The event callback for the current event should be called on the main browser thread. (0 == don't proxy)
206
206
case{{{cDefine('EM_CALLBACK_THREAD_CONTEXT_CALLING_THREAD')}}}: returnPThread.currentProxiedOperationCallerThread;// The event callback for the current event should be backproxied to the thread that is registering the event.
207
207
default: returntargetThread;// The event callback for the current event should be proxied to the given specific thread.
// beforeunload callback can only be registered on the main browser thread, because the page will go away immediately after returning from the handler,
2313
2313
// and there is no time to start proxying it anywhere.
0 commit comments