Whitelist instead of restricting to components for fileBrowserPrivate.

Whitelist instead of restricting to components for fileBrowserPrivate.

It is impossible to whitelist an extension which is note a component, when the
api is restricted to components. Since we need to whitelist such regular
extension, this patch removes the location restriction and whitelists all
clients of this API.

Along the way, id testing extensions using this api has been changed to a new
one, since it was reused with other tests not related to the api.

TEST=browser_tests: *FileBrowser*, *FileManager*
BUG=None

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

[mtomasz, 2014-09-25 05:06:06]

mtomasz@chromium.org changed reviewers:
+ hirono@chromium.org, miket@chromium.org

[mtomasz, 2014-09-25 05:06:06]

@miket: PTAL at chrome/common/extensions/api/_permission_features.json.
@hirono: PTAL at everything else.

Thanks.

[hirono, 2014-09-25 05:22:09]

On 2014/09/25 05:06:06, mtomasz wrote:
> @miket: PTAL at chrome/common/extensions/api/_permission_features.json.
> @hirono: PTAL at everything else.
> 
> Thanks.

Should we remove this?
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/ext_au...

[hirono, 2014-09-25 09:10:50]

On 2014/09/25 05:22:09, hirono wrote:
> On 2014/09/25 05:06:06, mtomasz wrote:
> > @miket: PTAL at chrome/common/extensions/api/_permission_features.json.
> > @hirono: PTAL at everything else.
> > 
> > Thanks.
> 
> Should we remove this?
>
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/ext_au...

The bug was filed. crbug.com/417604
Could you add comments showing actual extension ID to the manifest files? They
help someone to grep the ID to find the white list.

[mtomasz, 2014-09-25 09:43:40]

On 2014/09/25 09:10:50, hirono wrote:
> On 2014/09/25 05:22:09, hirono wrote:
> > On 2014/09/25 05:06:06, mtomasz wrote:
> > > @miket: PTAL at chrome/common/extensions/api/_permission_features.json.
> > > @hirono: PTAL at everything else.
> > > 
> > > Thanks.
> > 
> > Should we remove this?
> >
>
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/ext_au...
> 
> The bug was filed. crbug.com/417604
> Could you add comments showing actual extension ID to the manifest files? They
> help someone to grep the ID to find the white list.

Done. PTAL Thanks!
As for 417604, the extension is going to be removed.

[hirono, 2014-09-25 10:12:09]

On 2014/09/25 09:43:40, mtomasz wrote:
> On 2014/09/25 09:10:50, hirono wrote:
> > On 2014/09/25 05:22:09, hirono wrote:
> > > On 2014/09/25 05:06:06, mtomasz wrote:
> > > > @miket: PTAL at chrome/common/extensions/api/_permission_features.json.
> > > > @hirono: PTAL at everything else.
> > > > 
> > > > Thanks.
> > > 
> > > Should we remove this?
> > >
> >
>
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/ext_au...
> > 
> > The bug was filed. crbug.com/417604
> > Could you add comments showing actual extension ID to the manifest files?
They
> > help someone to grep the ID to find the white list.
> 
> Done. PTAL Thanks!
> As for 417604, the extension is going to be removed.

lgtm! Thank you!

[miket_OOO, 2014-09-25 16:45:14]

> @miket: PTAL at chrome/common/extensions/api/_permission_features.json.

This file LGTM

[mtomasz, 2014-09-25 23:04:08]

The CQ bit was checked by mtomasz@chromium.org

[commit-bot: I haz the power, 2014-09-25 23:06:48]

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

[commit-bot: I haz the power, 2014-09-25 23:20:56]

Committed patchset #4 (id:60001) as 79d29ee1ae86731221e3c228dd1deed53b7cb595

[commit-bot: I haz the power, 2014-09-25 23:21:42]

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