MD Settings: change how tap is handled on custom toggle rows

chrome/browser/resources/settings/privacy_page/privacy_page.html

Index: chrome/browser/resources/settings/privacy_page/privacy_page.html
diff --git a/chrome/browser/resources/settings/privacy_page/privacy_page.html b/chrome/browser/resources/settings/privacy_page/privacy_page.html
index c6c14a1e7eaf634b36fa131fafd34ff93636ba63..ae52f2a5c13e58cb212a4b2616a61032ff9d6fe1 100644
--- a/chrome/browser/resources/settings/privacy_page/privacy_page.html
+++ b/chrome/browser/resources/settings/privacy_page/privacy_page.html
@@ -82,9 +82,12 @@
           </settings-toggle-button>
         </div>
         <div class="settings-box">

[Dan Beam, 2017/02/08 23:12:04]

actionable or on-tap on the settings-box itself is a litttttle different than on
nearby <settings-toggle-box>

technically the closest would be if we made a wrapper <div> inside of <div
class="settings-box"> which would act similarly to <settings-toggle-button> as a
wrapper around <paper-toggle-button>, but I don't really see much benefit to
that

[dpapad, 2017/02/08 23:46:05]

Wrapping the <div> and the <paper-toggle-button> with another <div> would
probably break the effects of the "start" CSS class, no?

-          <div class="start">$i18n{safeBrowsingEnableExtendedReporting}</div>
+          <div class="start" on-tap="onSafeBrowsingExtendedReportingTap_"
+              actionable>
+            $i18n{safeBrowsingEnableExtendedReporting}
+          </div>
           <paper-toggle-button id="safeBrowsingExtendedReportingControl"
-              on-tap="onSafeBrowsingExtendedReportingControlTap_"
+              on-tap="onSafeBrowsingExtendedReportingTap_"
               checked="[[safeBrowsingExtendedReportingEnabled_]]">
           </paper-toggle-button>
         </div>
@@ -105,7 +108,10 @@
 </if><!-- chromeos -->
 <if expr="not chromeos">
         <div class="settings-box">

[Dan Beam, 2017/02/08 23:12:04]

in this case we really don't want on-tap on the settings-box or on a container
because it might affect the results as one is tapping the restart button (which
is a can of worms)

[dpapad, 2017/02/08 23:46:05]

I don't have a 100% understanding of our requirements. Here is the problem I see
with not having the tap handler on the settings-box: The click target is
narrower than the settings-box row, see http://imgur.com/a/eqOSI.

Q1: Is this Alan's original intention?
Q2: Regardless of yes/no, should we be consistent across all our settings-box
instances?

For example in settings-box instances that open a subpage the click target
covers the entire row, including the padding on the left, see
http://imgur.com/a/fO4bT.

If we want the entire row always be clickable, I don't see another option othen
than having the click/tap handler should be on settings-box, and any buttons
inside the row (like the 'restart' button), having to call stopPropagation().

[Dan Beam, 2017/02/09 00:27:40]

that's the same for all existing <settings-toggle-box>, afaik
unclear
yes, which is why I'm NOT using actionable on-top on the settings-box.
yes, understood, those are different that a majority of <settings-toggle-button>
I think we want consistency.

-          <div class="start">$i18n{enableLogging}</div>
+          <div class="start" on-tap="onMetricsReportingTap_"
+              actionable$="[[!metricsReporting_.managed]]">
+            $i18n{enableLogging}
+          </div>
           <template is="dom-if" if="[[showRestart_]]" restamp>
             <paper-button on-tap="onRestartTap_" id="restart">
               $i18n{restart}
@@ -119,7 +125,7 @@
             </paper-tooltip>
           </template>
           <paper-toggle-button id="metricsReportingControl"
-              on-tap="onMetricsReportingControlTap_"
+              on-tap="onMetricsReportingTap_"
               checked="[[metricsReporting_.enabled]]"
               disabled="[[metricsReporting_.managed]]">
           </paper-toggle-button>