DevTools: Sort execution contexts in nested frames

third_party/WebKit/Source/devtools/front_end/sdk/TargetManager.js

Index: third_party/WebKit/Source/devtools/front_end/sdk/TargetManager.js
diff --git a/third_party/WebKit/Source/devtools/front_end/sdk/TargetManager.js b/third_party/WebKit/Source/devtools/front_end/sdk/TargetManager.js
index 7e09dff47441da4e36f267bab42c7633ea003b02..8af0433809dd668e08dd731f400025422e874478 100644
--- a/third_party/WebKit/Source/devtools/front_end/sdk/TargetManager.js
+++ b/third_party/WebKit/Source/devtools/front_end/sdk/TargetManager.js
@@ -196,6 +196,8 @@ WebInspector.TargetManager.prototype = {
 
         /** @type {!WebInspector.ConsoleModel} */
         target.consoleModel = new WebInspector.ConsoleModel(target);
+        /** @type {!WebInspector.RuntimeModel} */
+        target.runtimeModel = new WebInspector.RuntimeModel(target);

[pfeldman, 2016/10/14 14:36:25]

With this, we broke one of the decorator assumptions - upon context creation, we
receive the frameId that has not been reported to the front-end (we initialize
resourceTreeModel below). This results in blank execution context names. Do you
remember why we moved it here?

[einbinder, 2016/10/14 18:07:38]

The ResourceTreeModel injects a callback into the runtimeModel for sorting
execution contexts by frames. 

 
         var networkManager = null;
         if (!target.isJSInspector())
@@ -207,8 +209,6 @@ WebInspector.TargetManager.prototype = {
         if (networkManager)
             new WebInspector.NetworkLog(target, networkManager);
 
-        /** @type {!WebInspector.RuntimeModel} */
-        target.runtimeModel = new WebInspector.RuntimeModel(target);
         if (target.hasJSContext())
             new WebInspector.DebuggerModel(target);