Organize security panel main view.

Source/devtools/front_end/main/Main.js

Index: Source/devtools/front_end/main/Main.js
diff --git a/Source/devtools/front_end/main/Main.js b/Source/devtools/front_end/main/Main.js
index ed1907289f2c6d0bc36942b7a4a1bc8c27b89b6d..d80709edfaccc60ad065f5b434833cec8eb42bd5 100644
--- a/Source/devtools/front_end/main/Main.js
+++ b/Source/devtools/front_end/main/Main.js
@@ -138,7 +138,7 @@ WebInspector.Main.prototype = {
         Runtime.experiments.register("networkRequestsOnTimeline", "Network requests on Timeline", true);
         Runtime.experiments.register("privateScriptInspection", "Private script inspection");
         Runtime.experiments.register("promiseTracker", "Promise inspector");
-        Runtime.experiments.register("securityPanel", "Security panel", true);
+        Runtime.experiments.register("securityPanel", "Security panel");

[lgarron, 2015/08/26 04:17:18]

Paul: if I recall correctly, you were interested in changing the securityPanel
to a non-hidden experiment and merging to M46 along with
https://codereview.chromium.org/1301833003 (and Pavel didn't feel strongly, as
long as we don't ship with a yellow icon before we remove the experimental flag
altogether). Still the case?

[dgozman, 2015/08/26 20:28:41]

If you plan to merge to M46, create a separate patch with just this change.

[lgarron, 2015/08/26 21:42:43]

That would mean three merges instead of two. Is that preferred?

         Runtime.experiments.register("serviceWorkersInResources", "Service workers in Resources panel", true);
         Runtime.experiments.register("showPrimaryLoadWaterfallInNetworkTimeline", "Show primary load waterfall in Network timeline", true);
         Runtime.experiments.register("stepIntoAsync", "Step into async");