At the all-hands :baku proposed making nsIGlobalObject the public interface, with the intent to move even worker-specific things to this interface like Terminate(). That seems like an excellent plan to me.
Bug 1350337 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
At the all-hands :baku proposed making nsIGlobalObject the public interface, with the intent to move even worker-specific things to this interface like Terminate(). That seems like an excellent plan to me. edit, much later: nsIGlobalObject is not something we can safely use on the parent thread (or other threads), so although nsIGlobalObject is an appropriate interface for logic *on the worker thread*, it's definitely the case that there are other use-cases where this is not appropriate. Like the `Worker` binding held by the parent could not/must not use nsIGlobalObject. There is also the RuntimeService set of use-cases that ideally would be a separate interface because of our plans for the new IPDL protocols for things like sending debugger control messages via IPC rather than via direct runnables.