Hack to fix settings-checkbox mixin for 1.6.0

chrome/browser/resources/settings/controls/settings_checkbox.html

Index: chrome/browser/resources/settings/controls/settings_checkbox.html
diff --git a/chrome/browser/resources/settings/controls/settings_checkbox.html b/chrome/browser/resources/settings/controls/settings_checkbox.html
index fb3378372b15b3a3035818b292a2f50e1cc9976a..0acdf3da05e314fd7641dcb6186b9aac83099f6c 100644
--- a/chrome/browser/resources/settings/controls/settings_checkbox.html
+++ b/chrome/browser/resources/settings/controls/settings_checkbox.html
@@ -20,6 +20,13 @@
         @apply(--settings-secondary);
       }
 
+      #nonexistent {
+        /* HACK(michaelpg): Inform Polymer that this mixin can set "display". */

[Dan Beam, 2016/07/23 00:12:29]

why does this need a #nonexistent, and not just be the default style, i.e.

:host {
  --settings-secondary-unchecked: {
    display: block;
  };
}

[Dan Beam, 2016/07/23 00:14:15]

or even better, display: initial;

[1] https://developer.mozilla.org/en-US/docs/Web/CSS/initial

[michaelpg, 2016/07/23 00:15:23]

That would override the mixin, and the checkbox would always be display: block.
We don't want to actually *set* the mixin; this is just a hack that tells
Polymer to let "display" work.

The bug is, basically, that Polymer only shims properties in a mixin **that are
included in the mixin in the first element that references the mixin**.

+        --settings-secondary-unchecked: {
+          display: block;
+        };
+      }
+
       paper-checkbox:not([checked]) .secondary {
         @apply(--settings-secondary-unchecked);
       }