mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
a4ec7a6646
If we just naively use the thread manager to dispatch the event via SpecialPowers, we cannot avoid the XPCWrappedJS for the runnable being in chrome scope (even if we pass a content object, we make the call in chrome scope, so we pass a cross- compartment wrapper). This means that the machinery in nsXPCWrappedJSClass::CheckForException ends up calling the error reporter for the SpecialPowers scope, which isn't what we want. Messing around with the implementation of CheckForException is playing with fire. So we work around this with an explicit Cu API. :-( |
||
|---|---|---|
| .. | ||
| Makefile.in | ||
| mozIJSSubScriptLoader.idl | ||
| nsIJSContextStack.idl | ||
| nsIJSEngineTelemetryStats.idl | ||
| nsIJSRuntimeService.idl | ||
| nsIScriptError.idl | ||
| nsIXPConnect.idl | ||
| nsIXPCScriptable.idl | ||
| nsIXPCScriptNotify.idl | ||
| nsIXPCSecurityManager.idl | ||
| xpccomponents.idl | ||
| xpcexception.idl | ||
| xpcIJSGetFactory.idl | ||
| xpcIJSModuleLoader.idl | ||
| xpcIJSWeakReference.idl | ||
| xpcjsid.idl | ||