Fix DevTools support of worklets

third_party/WebKit/Source/core/inspector/MainThreadDebugger.cpp

Index: third_party/WebKit/Source/core/inspector/MainThreadDebugger.cpp
diff --git a/third_party/WebKit/Source/core/inspector/MainThreadDebugger.cpp b/third_party/WebKit/Source/core/inspector/MainThreadDebugger.cpp
index 763f4fa9588f72f869aaad9db6bd28744b79e25c..2c218b01a4e4406882d9fe69abfbff487bc4c0f0 100644
--- a/third_party/WebKit/Source/core/inspector/MainThreadDebugger.cpp
+++ b/third_party/WebKit/Source/core/inspector/MainThreadDebugger.cpp
@@ -188,8 +188,8 @@ bool MainThreadDebugger::callingContextCanAccessContext(v8::Local<v8::Context> c
     ASSERT(executionContext);
 
     if (executionContext->isMainThreadWorkletGlobalScope()) {
-        MainThreadWorkletGlobalScope* globalScope = toMainThreadWorkletGlobalScope(executionContext);
-        return globalScope && BindingSecurity::shouldAllowAccessTo(m_isolate, toLocalDOMWindow(toDOMWindow(calling)), globalScope, DoNotReportSecurityError);
+        // Similar to WorkerThreadDebugger::callingContextCanAccessContext(http://crrev.com/1638563002).

[dgozman, 2016/06/13 13:14:06]

We can return |true| in workers just because we know that it's isolate contains
only a single worker, so any access is allowed. Here in main thread isolate, we
may have a lot of different pages (possibly with worklets), so access check is
required. I think, we should retrieve a LocalDOMWindow for both calling and
target regardless of whether they are worklets or not, and then ask
BindingSecurity.

+        return true;
     }
 
     DOMWindow* window = toDOMWindow(target);