Remove unused "Website Settings" view of content settings

Remove unused "Website Settings" view of content settings

This code has been unused for 8+months.

BUG=492024
Committed: https://crrev.com/9a66ed01a85062d9ed2a70138597825bd1e4651f
Cr-Commit-Position: refs/heads/master@{#332150}

[raymes, 2015-05-26 05:09:46]

raymes@chromium.org changed reviewers:
+ markusheintz@chromium.org, scheib@chromium.org

[raymes, 2015-05-26 05:54:56]

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

[raymes, 2015-05-26 05:54:57]

+jhawkins/tbuckley. Please let me know if you think we would want to keep any of
this code for the settings UI redesign.

Thanks!

[James Hawkins, 2015-05-26 17:59:00]

On 2015/05/26 05:54:57, raymes wrote:
> +jhawkins/tbuckley. Please let me know if you think we would want to keep any
of
> this code for the settings UI redesign.
> 
> Thanks!

Removal looks good.

[scheib, 2015-05-27 01:11:41]

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

[commit-bot: I haz the power, 2015-05-27 01:12:22]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1156983002/40001

[commit-bot: I haz the power, 2015-05-27 02:10:09]

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

[commit-bot: I haz the power, 2015-05-27 02:10:10]

Dry run: This issue passed the CQ dry run.

[raymes, 2015-05-27 02:28:52]

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

[raymes, 2015-05-27 02:28:52]

Markus/Martin does this seem ok to you guys? If so I will get OWNERS approval.

Thanks!
Raymes

[scheib, 2015-05-27 04:29:35]

On 2015/05/27 02:28:52, raymes wrote:
> Markus/Martin does this seem ok to you guys? If so I will get OWNERS approval.
> 
> Thanks!
> Raymes

As mentioned on email thread - generally looks good to me as well, but approval
should come from folks working on that system, so I'm taking myself off reviewer
list.

[scheib, 2015-05-27 04:30:08]

scheib@chromium.org changed reviewers:
- scheib@chromium.org

[msramek, 2015-05-27 17:01:53]

LGTM in the sense that I don't expect the code to be needed, but people working
on the new UI should confirm :)

[raymes, 2015-05-28 03:56:19]

On 2015/05/27 17:01:53, msramek wrote:
> LGTM in the sense that I don't expect the code to be needed, but people
working
> on the new UI should confirm :)

jhawkins is working on the new UI and confirmed above :) Thanks!

[raymes, 2015-05-28 03:59:12]

jhawkins: could you please give OWNERS for the stuff in chrome/

markusheintz: could you please give OWNERS for the stuff in
components/content_settings

Thanks!

[markusheintz_, 2015-05-29 15:24:04]

On 2015/05/28 03:59:12, raymes wrote:
> jhawkins: could you please give OWNERS for the stuff in chrome/
> 
> markusheintz: could you please give OWNERS for the stuff in
> components/content_settings
> 
> Thanks!

LGTM

[markusheintz_, 2015-05-29 15:24:07]

On 2015/05/28 03:59:12, raymes wrote:
> jhawkins: could you please give OWNERS for the stuff in chrome/
> 
> markusheintz: could you please give OWNERS for the stuff in
> components/content_settings
> 
> Thanks!

LGTM

[markusheintz_, 2015-05-29 15:26:05]

markusheintz@chromium.org changed reviewers:
+ felt@chromium.org

[markusheintz_, 2015-05-29 15:26:38]

On 2015/05/29 15:24:07, markusheintz_ wrote:
> On 2015/05/28 03:59:12, raymes wrote:
> > jhawkins: could you please give OWNERS for the stuff in chrome/
> > 
> > markusheintz: could you please give OWNERS for the stuff in
> > components/content_settings
> > 
> > Thanks!
> 
> LGTM

Adding Adrienne: Do you know if this code is still needed?

[James Hawkins, 2015-05-29 16:39:26]

lgtm

[felt, 2015-05-29 17:24:54]

Based on a recent thread about this code, it's OK to delete because the Material
Design revamp is replacing it.

[James Hawkins, 2015-05-29 17:31:39]

On 2015/05/29 17:24:54, felt wrote:
> Based on a recent thread about this code, it's OK to delete because the
Material
> Design revamp is replacing it.

To clarify, the new MD Settings team is not implementing parts of the UI that
are currently behind a flag, including the feature being removed in this CL.

[felt, 2015-05-29 17:46:51]

On 2015/05/29 17:31:39, James Hawkins wrote:
> On 2015/05/29 17:24:54, felt wrote:
> > Based on a recent thread about this code, it's OK to delete because the
> Material
> > Design revamp is replacing it.
> 
> To clarify, the new MD Settings team is not implementing parts of the UI that
> are currently behind a flag, including the feature being removed in this CL.

My understanding was that the MD Settings team is going to implement this:
https://folio.googleplex.com/chrome-ux/mocks/236-fizz/content-settings/022015...

Which is extremely similar to what's being removed in this CL. Am I
misunderstanding what's being deleted in this CL, or is there confusion over
who's implementing those mocks?

[James Hawkins, 2015-05-29 17:49:47]

On 2015/05/29 17:46:51, felt wrote:
> On 2015/05/29 17:31:39, James Hawkins wrote:
> > On 2015/05/29 17:24:54, felt wrote:
> > > Based on a recent thread about this code, it's OK to delete because the
> > Material
> > > Design revamp is replacing it.
> > 
> > To clarify, the new MD Settings team is not implementing parts of the UI
that
> > are currently behind a flag, including the feature being removed in this CL.
> 
> My understanding was that the MD Settings team is going to implement this:
>
https://folio.googleplex.com/chrome-ux/mocks/236-fizz/content-settings/022015...
> 
> Which is extremely similar to what's being removed in this CL. Am I
> misunderstanding what's being deleted in this CL, or is there confusion over
> who's implementing those mocks?

Neither.  I hadn't made the connection between these two.

[felt, 2015-05-29 17:51:03]

On 2015/05/29 17:49:47, James Hawkins wrote:
> On 2015/05/29 17:46:51, felt wrote:
> > On 2015/05/29 17:31:39, James Hawkins wrote:
> > > On 2015/05/29 17:24:54, felt wrote:
> > > > Based on a recent thread about this code, it's OK to delete because the
> > > Material
> > > > Design revamp is replacing it.
> > > 
> > > To clarify, the new MD Settings team is not implementing parts of the UI
> that
> > > are currently behind a flag, including the feature being removed in this
CL.
> > 
> > My understanding was that the MD Settings team is going to implement this:
> >
>
https://folio.googleplex.com/chrome-ux/mocks/236-fizz/content-settings/022015...
> > 
> > Which is extremely similar to what's being removed in this CL. Am I
> > misunderstanding what's being deleted in this CL, or is there confusion over
> > who's implementing those mocks?
> 
> Neither.  I hadn't made the connection between these two.

OK, so we should be good to go then, yes?

[James Hawkins, 2015-05-29 17:55:04]

On 2015/05/29 17:51:03, felt wrote:
> On 2015/05/29 17:49:47, James Hawkins wrote:
> > On 2015/05/29 17:46:51, felt wrote:
> > > On 2015/05/29 17:31:39, James Hawkins wrote:
> > > > On 2015/05/29 17:24:54, felt wrote:
> > > > > Based on a recent thread about this code, it's OK to delete because
the
> > > > Material
> > > > > Design revamp is replacing it.
> > > > 
> > > > To clarify, the new MD Settings team is not implementing parts of the UI
> > that
> > > > are currently behind a flag, including the feature being removed in this
> CL.
> > > 
> > > My understanding was that the MD Settings team is going to implement this:
> > >
> >
>
https://folio.googleplex.com/chrome-ux/mocks/236-fizz/content-settings/022015...
> > > 
> > > Which is extremely similar to what's being removed in this CL. Am I
> > > misunderstanding what's being deleted in this CL, or is there confusion
over
> > > who's implementing those mocks?
> > 
> > Neither.  I hadn't made the connection between these two.
> 
> OK, so we should be good to go then, yes?

Yep, slgtm

[raymes, 2015-06-01 00:20:15]

On 2015/05/29 17:55:04, James Hawkins wrote:
> On 2015/05/29 17:51:03, felt wrote:
> > On 2015/05/29 17:49:47, James Hawkins wrote:
> > > On 2015/05/29 17:46:51, felt wrote:
> > > > On 2015/05/29 17:31:39, James Hawkins wrote:
> > > > > On 2015/05/29 17:24:54, felt wrote:
> > > > > > Based on a recent thread about this code, it's OK to delete because
> the
> > > > > Material
> > > > > > Design revamp is replacing it.
> > > > > 
> > > > > To clarify, the new MD Settings team is not implementing parts of the
UI
> > > that
> > > > > are currently behind a flag, including the feature being removed in
this
> > CL.
> > > > 
> > > > My understanding was that the MD Settings team is going to implement
this:
> > > >
> > >
> >
>
https://folio.googleplex.com/chrome-ux/mocks/236-fizz/content-settings/022015...
> > > > 
> > > > Which is extremely similar to what's being removed in this CL. Am I
> > > > misunderstanding what's being deleted in this CL, or is there confusion
> over
> > > > who's implementing those mocks?
> > > 
> > > Neither.  I hadn't made the connection between these two.
> > 
> > OK, so we should be good to go then, yes?
> 
> Yep, slgtm

Thanks all. Sorry it was confusing!

[raymes, 2015-06-01 00:20:23]

The CQ bit was checked by raymes@chromium.org

[commit-bot: I haz the power, 2015-06-01 00:20:31]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1156983002/40001

[commit-bot: I haz the power, 2015-06-01 01:32:33]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-06-01 01:33:19]

Patchset 3 (id:??) landed as
https://crrev.com/9a66ed01a85062d9ed2a70138597825bd1e4651f
Cr-Commit-Position: refs/heads/master@{#332150}