MD History: Show sidebar next to content on wide screens

chrome/browser/resources/md_history/history_toolbar.js

Index: chrome/browser/resources/md_history/history_toolbar.js
diff --git a/chrome/browser/resources/md_history/history_toolbar.js b/chrome/browser/resources/md_history/history_toolbar.js
index 9562c754ffc3a5706497e956fb8a73d3a0020839..fd6f035afc69c4fd7a5d8db2ac40dd04773de270 100644
--- a/chrome/browser/resources/md_history/history_toolbar.js
+++ b/chrome/browser/resources/md_history/history_toolbar.js
@@ -34,6 +34,12 @@ Polymer({
       value: false
     },
 
+    hasDrawer: {
+      type: Boolean,
+      observer: 'hasDrawerChanged_',
+      reflectToAttribute: true,
+    },
+
     // Whether domain-grouped history is enabled.
     isGroupedMode: {
       type: Boolean,
@@ -122,5 +128,10 @@ Polymer({
     // TODO(calamity): Fix the format of these dates.
     return loadTimeData.getStringF(
       'historyInterval', queryStartTime, queryEndTime);
-  }
+  },
+
+  /** @private */
+  hasDrawerChanged_: function() {
+    this.updateStyles();

[calamity, 2016/07/26 05:05:18]

Why is this necessary? Shouldn't the attribute reflection just update the styles
accordingly?

[tsergeant, 2016/07/26 05:59:03]

Nope. The polymer custom style shim isn't always able to propagate dynamic
changes automatically
(https://www.polymer-project.org/1.0/docs/devguide/styling#custom-properties-s...).

I think this will be unnecessary when we turn native custom properties on,
though.

+  },
 });