Whitelist extension APIs from md-settings in settings

Whitelist extension APIs from md-settings in settings

If the MaterialDesignSettings feature is enabled, chrome://settings loads
MD settings, so whitelist extension APIs there too.

The test will involve adding the MaterialDesignSettings feature and
checking for console errors. Looking into the best way to do that.

BUG=627932
R=dbeam@chromium.org

Committed: https://crrev.com/e88ced52cb6cfc584882b726f142b13db97d2f1c
Cr-Commit-Position: refs/heads/master@{#405332}

[michaelpg, 2016-07-13 20:18:36]

this whitelists new APIs in old Settings if MaterialDesignSettings is not
enabled... is that OK?

[Dan Beam, 2016-07-13 21:24:58]

yeah, probably fine

lgtm

/cc rdevlin.cronin@ as fyi (we're opening up some private extension APIs for
chrome://settings, which might also allow the old page access as well -- don't
think it's a big deal)

[Devlin, 2016-07-13 21:27:04]

On 2016/07/13 21:24:58, Dan Beam wrote:
> yeah, probably fine
> 
> lgtm
> 
> /cc rdevlin.cronin@ as fyi (we're opening up some private extension APIs for
> chrome://settings, which might also allow the old page access as well -- don't
> think it's a big deal)

yeah, settings already has the power to totally bork you, so this isn't much
worse. lgtm

[michaelpg, 2016-07-13 21:29:04]

The CQ bit was checked by michaelpg@chromium.org

[commit-bot: I haz the power, 2016-07-13 21:30:21]

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

[commit-bot: I haz the power, 2016-07-13 22:56:26]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-13 22:59:08]

Description was changed from

==========
Whitelist extension APIs from md-settings in settings

If the MaterialDesignSettings feature is enabled, chrome://settings loads
MD settings, so whitelist extension APIs there too.

The test will involve adding the MaterialDesignSettings feature and
checking for console errors. Looking into the best way to do that.

BUG=627932
R=dbeam@chromium.org
==========

to

==========
Whitelist extension APIs from md-settings in settings

If the MaterialDesignSettings feature is enabled, chrome://settings loads
MD settings, so whitelist extension APIs there too.

The test will involve adding the MaterialDesignSettings feature and
checking for console errors. Looking into the best way to do that.

BUG=627932
R=dbeam@chromium.org

Committed: https://crrev.com/e88ced52cb6cfc584882b726f142b13db97d2f1c
Cr-Commit-Position: refs/heads/master@{#405332}
==========

[commit-bot: I haz the power, 2016-07-13 22:59:12]

Patchset 1 (id:??) landed as
https://crrev.com/e88ced52cb6cfc584882b726f142b13db97d2f1c
Cr-Commit-Position: refs/heads/master@{#405332}