Enhancements to https://codereview.chromium.org/12494033/ for zmo@

chrome/browser/resources/options/pref_ui.js

Index: chrome/browser/resources/options/pref_ui.js
diff --git a/chrome/browser/resources/options/pref_ui.js b/chrome/browser/resources/options/pref_ui.js
index dd33c72eab21e0c26ef39363d934fe6ba66afae7..45ac11aef860ba5cae47525f82044dd7e5f6739a 100644
--- a/chrome/browser/resources/options/pref_ui.js
+++ b/chrome/browser/resources/options/pref_ui.js
@@ -180,7 +180,10 @@ cr.define('options', function() {
      */
     updateStateFromPref_: function(event) {
       var value = Boolean(event.value.value);
+      var checked = this.checked;
       this.checked = this.inverted_pref ? !value : value;
+      if (checked != this.checked)

[Dan Beam, 2013/03/22 00:31:29]

arv@: this is mildly alarming

[arv (Not doing code reviews), 2013/03/22 14:35:48]

Yeah, this is wrong. We already have code in place for updating the UI when a
pref changes, we should not simulate user actions.

+        cr.dispatchSimpleEvent(this, 'change', true, true);
     },
   };