[subresource_filter] Revamp Site Details page

[subresource_filter] Revamp Site Details page

The subresource filter site details page has a few custom requirements.
- Allow and Block strings have two variants, active and passive. Which
  one to use depends on whether the site is currently activated for
  subresource filtering.

- The radio dialog always uses the passive strings

These constraints led to the creation of a ChromeBaseListPreference
subclass that changes its underlying string entries dynamically based
on activation and whether the radio dialog is showing.

BUG=689487

[Charlie Harrison, 2017-05-15 02:50:22]

The CQ bit was checked by csharrison@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-15 02:50:28]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Charlie Harrison, 2017-05-15 02:53:20]

csharrison@chromium.org changed reviewers:
+ raymes@chromium.org

[Charlie Harrison, 2017-05-15 02:53:21]

raymes: This is the most substantial of the settings UI changes. No tests yet
but I wanted to get some high level feedback first. Does the approach make
sense?

[commit-bot: I haz the power, 2017-05-15 04:42:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-15 04:42:48]

Dry run: Try jobs failed on following builders:
  android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)

[Charlie Harrison, 2017-05-15 15:18:09]

We decided not to go this route.

I'm closing this issue instead of modifying it for posterity, because someone
(maybe us) might want to do this in the future and this will be a nice template
of a solution.

[Charlie Harrison, 2017-05-15 15:18:26]

Description was changed from

==========
[subresource_filter] Revamp Site Details page

The subresource filter site details page has a few custom requirements.
- Allow and Block strings have two variants, active and passive. Which
  one to use depends on whether the site is currently activated for
  subresource filtering.

- The radio dialog always uses the passive strings

These constraints led to the creation of a ChromeBaseListPreference
subclass that changes its underlying string entries dynamically based
on activation and whether the radio dialog is showing.

BUG=689487
==========

to

==========
[subresource_filter] Revamp Site Details page

The subresource filter site details page has a few custom requirements.
- Allow and Block strings have two variants, active and passive. Which
  one to use depends on whether the site is currently activated for
  subresource filtering.

- The radio dialog always uses the passive strings

These constraints led to the creation of a ChromeBaseListPreference
subclass that changes its underlying string entries dynamically based
on activation and whether the radio dialog is showing.

BUG=689487
==========