Fix empty candidate window for IME Extension API.

Fix empty candidate window for IME Extension API.

The problem is that some engines are never deactivated when the engine is switched.
The original IBus spec assumes each engine instance will be created on CreateEngine method and destroyed on Destroy function.
However in the case of Chrome, we switch the engine instance at the next CreateEngine function and no-op for Destroy function.
This is ideally okay because there is only one engine instance.
However ibus-daemon sends "Disable" message *AFTER* CreateEngine function, so Extension IME missed it, this is the root cause.

I changed to calling "Disable" function at the instance switching and it fixes this problem.

BUG=182916
TEST=Manually checked on lumpy.


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

[Zachary Kuznia, 2013-03-12 11:49:12]

lgtm

[commit-bot: I haz the power, 2013-03-12 12:17:30]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nona@chromium.org/12598004/1

[commit-bot: I haz the power, 2013-03-12 17:01:11]

Step "update" is always a major failure.
Look at the try server FAQ for more details.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

[commit-bot: I haz the power, 2013-03-12 17:51:09]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nona@chromium.org/12598004/1

[commit-bot: I haz the power, 2013-03-12 22:58:22]

Change committed as 187680