Okay, our stance on this UI might need some modification now that we've made checkboxes to switches and restricted card width.

Prior to the above changes, we had controls on the left and right hand side of the row with potentially 920px between each control. We allowed a click in the row to "activate" what was considered A LOT of dead space. I think that was the right call then but we now live in a pretty different UI. 

All controls (excluding dialogs and on startup) have controls on the right hand side and the card width is restricted to 640px. The notion to make the entire row clickable seems less important and arguably less intuitive now. (If we were to heatmap a row with a switch, I hypothesize that it's most likely that users will direct their clicks/taps to the actual switch and not the whitespace around it)

I think this will simplify our settings.box model as well: 

1. Unactionable row - text, text with hyperlinks 
2. Unactionable row with component - switches, dropdowns

3. Actionable row - subpage-arrow, outlinks, radio btns, and drop-down arrow (soon to be deprecated)
4. Actionable with component - two actionable parts divided by a rule line

@bettes why should rows with switches not be actionable? For example, tapping anywhere on a switch row in Android Settings will toggle the switch.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3245561158dde6808bd24b3322304369af52abac

commit 3245561158dde6808bd24b3322304369af52abac
Author: dbeam <dbeam@chromium.org>
Date: Tue Feb 14 08:49:01 2017

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

R=scottchen@chromium.org
BUG= 680406 ,689763
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2684853003
Cr-Commit-Position: refs/heads/master@{#450293}

[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/browser/resources/settings/controls/settings_boolean_control_behavior.js
[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/browser/resources/settings/controls/settings_checkbox.html
[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/browser/resources/settings/controls/settings_toggle_button.html
[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/browser/resources/settings/controls/settings_toggle_button.js
[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/browser/resources/settings/privacy_page/compiled_resources2.gyp
[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/browser/resources/settings/privacy_page/privacy_page.html
[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/browser/resources/settings/privacy_page/privacy_page.js
[modify] https://crrev.com/3245561158dde6808bd24b3322304369af52abac/chrome/test/data/webui/settings/metrics_reporting_tests.js

Re comment #2, we agreed in the Settings UX sync that rows with switches should be actionable -- clicking the text should toggle the switch. All other decisions from that comment are unchanged.

Marking this as fixed, but we should refer to this for related decisions in future.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Clearing my ownership of P3 UI>Settings bugs. Feel free to re-assign once triaging is complete.