Enable TsfBridge to re-initialize

Enable TsfBridge to re-initialize

Currently we cannot re-initialize TsfBridge once
TsfBridge::Shutdown is called.
This patch set gets rid of such limitation.
This is mainly for unit test, where TsfBridge::Initialize
is called in its Setup function.

BUG=246534
TEST=Manually done with GoogleJapaneseInput.

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

[Seigo Nonaka, 2013-06-10 02:36:27]

On 2013/06/07 15:14:05, Yohei Yukawa wrote:

Sorry, could you add more description about why we need re-initialize TsfBridge.
If this is intended for testing, is TsfBridge::ReplaceForTesting not sufficient?

[Yohei Yukawa, 2013-06-10 02:47:00]

On 2013/06/10 02:36:27, Seigo Nonaka wrote:
> On 2013/06/07 15:14:05, Yohei Yukawa wrote:
> 
> Sorry, could you add more description about why we need re-initialize
TsfBridge.
> If this is intended for testing, is TsfBridge::ReplaceForTesting not
sufficient?

Yes, this is for unittest. Current Setup functions does not call
TsfBridge::ReplaceForTesting
Do you know why?

[Seigo Nonaka, 2013-06-10 03:19:13]

On 2013/06/10 02:47:00, Yohei Yukawa wrote:
> On 2013/06/10 02:36:27, Seigo Nonaka wrote:
> > On 2013/06/07 15:14:05, Yohei Yukawa wrote:
> > 
> > Sorry, could you add more description about why we need re-initialize
> TsfBridge.
> > If this is intended for testing, is TsfBridge::ReplaceForTesting not
> sufficient?
> 
> Yes, this is for unittest. Current Setup functions does not call
> TsfBridge::ReplaceForTesting
> Do you know why?

IMO, no need to replace to mock object in all test case.
This is an use case of MockTsfBridge. Even currently disabled:(
https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/re...

Anyway, as we chatted, we need multiple Shutdown/Initialize for unit tests.
So looks good to me.

[Seigo Nonaka, 2013-06-10 03:19:19]

lgtm

[Yohei Yukawa, 2013-06-10 12:48:09]

+sky@ for the owner review.
Could you take a look?

[sky, 2013-06-10 14:43:51]

LGTM

[commit-bot: I haz the power, 2013-06-10 14:44:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/Yukawa@chromium.org/16648002/13001

[commit-bot: I haz the power, 2013-06-10 19:25:21]

Change committed as 205271