Delay determination of why a synced disabled extension was disabled.

Delay determination of why a synced disabled extension was disabled.

Also simplify handling of legacy disabled extensions.

BUG=162062
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=171072

[Yoyo Zhou, 2012-11-29 02:43:59]

Do you know of any tests I could look at emulating that install an extension in
one profile and sync it to another?

[akalin, 2012-11-30 00:33:35]

On 2012/11/29 02:43:59, Yoyo Zhou wrote:
> Do you know of any tests I could look at emulating that install an extension
in
> one profile and sync it to another?

The integration tests do that; see two_client_extensions_sync_test.cc.

But I'd try to write a plain unit test that exercises this logic, if possible.

[Yoyo Zhou, 2012-12-01 00:54:07]

Unsurprisingly, adding a test showed that my first attempt was incorrect. Sadly,
it's more correct but more complex now.

It's quite the runabout to install an extension from sync in a browser test..

[akalin, 2012-12-04 17:21:12]

On 2012/12/01 00:54:07, Yoyo Zhou wrote:
> Unsurprisingly, adding a test showed that my first attempt was incorrect.
Sadly,
> it's more correct but more complex now.
> 
> It's quite the runabout to install an extension from sync in a browser test..

This LGTM from the sync side.  But can you get someone on the extensions team to
look over it, too?  I guess you need to for OWNERS anyway.

[Yoyo Zhou, 2012-12-04 18:21:54]

+mpcomplete

[Matt Perry, 2012-12-04 18:31:48]

lgtm

[commit-bot: I haz the power, 2012-12-04 19:37:57]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/yoz@chromium.org/11412239/7009

[commit-bot: I haz the power, 2012-12-04 22:53:51]

Change committed as 171072