Currently JSGlobalObjects always set remote inspection enabled in construction, and then JSDOMGlobalObjects would disable it. Instead move the remote inspection enabling on JSGlobalObjects to the JSContext/JSGlobalContextRef API boundaries. This way the JSGlobalObject within web pages are never temporarily debuggable reducing the amount of churn surrounding toggling this setting. This does mean that only JSGlobalObjects made through the JSC C/ObjC APIs are debuggable, but that covers the majority. I found only jsc directly instantiates a JSGlobalObject via subclassing.
<rdar://problem/18359599>
Created attachment 238221 [details] [PATCH] Proposed Fix
Comment on attachment 238221 [details] [PATCH] Proposed Fix View in context: https://bugs.webkit.org/attachment.cgi?id=238221&action=review > Source/JavaScriptCore/ChangeLog:10 > + Set the defaultl remote debuggable state at the API boundary. Typo: default
Comment on attachment 238221 [details] [PATCH] Proposed Fix Clearing flags on attachment: 238221 Committed r173683: <http://trac.webkit.org/changeset/173683>
All reviewed patches have been landed. Closing bug.