Make managedMode extension API component-only.

Make managedMode extension API component-only.

To use the API in an extension now, load it as a component extension via --load-component-extension.

BUG=115448
TEST=none


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=133926

[Bernhard Bauer, 2012-04-25 11:39:33]

Please review. Thanks!

[Finnur, 2012-04-25 14:25:20]

The change LGTM but is there a discussion/decision anywhere that confirms we
think now is the right time for it to graduate from experimental?

[Bernhard Bauer, 2012-04-25 14:33:04]

On 2012/04/25 14:25:20, Finnur wrote:
> The change LGTM but is there a discussion/decision anywhere that confirms we
> think now is the right time for it to graduate from experimental?

Making it component-only implies that it can't be used by third-party
extensions, right? So I'm not thinking of this CL as graduating the API from
experimental, but rather hiding it even further (because the first version of
the extension is likely going to be a component anyway).

Alternatively, if having experimental component extensions makes sense, I could
do that as well.

[Finnur, 2012-04-25 14:42:06]

No, it's just that I'm always hesitant about making a call to graduate something
as I'm not involved in any of the related decisions/discussion (and the bug you
link to is old and marked fixed). In this case it should be ok. I don't see the
point of having it experimental + component...

[commit-bot: I haz the power, 2012-04-25 15:12:46]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/bauerb@chromium.org/10141008/9001

[commit-bot: I haz the power, 2012-04-25 16:41:25]

Change committed as 133926