[Media Router] Custom Controls 4 - Implement details view WebUI

chrome/browser/resources/media_router/elements/route_details/route_details.html

 <link rel="import" href="chrome://resources/html/polymer.html">
 <link rel="import" href="chrome://resources/html/i18n_behavior.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/paper-button/paper-button.html">
+<link rel="import" href="extension_view_wrapper/extension_view_wrapper.html">
+<link rel="import" href="../route_controls/route_controls.html">
 <dom-module id="route-details">
   <link rel="import" type="css" href="../../media_router_common.css">
   <link rel="import" type="css" href="route_details.css">
   <template>
-    <div id="route-information" hidden$="[[!isCustomControllerHidden_]]">
+    <div id="route-information"
+        hidden$="[[!shouldShowRouteInfoOnly_(controllerType_)]]">
       <span>[[activityStatus_]]</span>
     </div>
-    <extensionview id="custom-controller"
-        hidden$="[[isCustomControllerHidden_]]">
-    </extensionview>
+    <template is="dom-if" if="[[!useWebUiRouteControls]]">
+      <extension-view-wrapper id="extension-view-wrapper" route="[[route]]"
+          is-extension-view-ready="{{isExtensionViewReady}}"
+          hidden$="[[!shouldShowExtensionView_(controllerType_)]]">
+      </extension-view-wrapper>
+    </template>
+    <route-controls id="route-controls"

[apacible, 2017/05/17 21:52:17]

What are the pros/cons of keeping <route-controls> out of a dom-if template? Are
we more likely to use the route-controls? What is performance difference like?

[takumif, 2017/05/18 18:01:55]

Actually, since we'll be comparing the load times against extensionview it'd
make sense to put it in dom-if as well. Doing that, and when we remove
extensionview entirely, we'll take it out of dom-if again. Putting
route-controls in dom-if seems to increase its load time by ~50ms.

[apacible, 2017/05/24 20:28:26]

SGTM.

+        hidden$="[[!shouldShowWebUiControls_(controllerType_)]]">
+    </route-controls>
     <div id="route-action-buttons" class="layout">
       <paper-button flat class="route-button button"
           id="start-casting-to-route-button"
           hidden$="[[computeCastButtonHidden_(route, changeRouteSourceAvailable_)]]"
           on-tap="startCastingToRoute_">
         <span>[[i18n('startCastingButtonText')]]</span>
       </paper-button>
       <paper-button flat class="route-button button"
           id="close-route-button"
           on-tap="closeRoute_">
         <span>[[i18n('stopCastingButtonText')]]</span>
       </paper-button>
     <div>
   </template>
 <script src="route_details.js"></script>
 </dom-module>