rule-based: Add new API for the extension to reset the engine state.
Right now, the extension may need to reset the state of an engine w/o deactivating it. For example, if the user starts voice input, we need to reset the engine state (voice input is not an engine; if it was an engine, everything will work because we would deactivate the current engine before starting voice input). So far, this has been fine because the extension contained both UI and IME code. But when we move to a native model, UI will no longer contain IME code, so it will need to signal to IMF to reset the state of the engine. We add a new private API for resetting the engine. Bug: 1009903 Change-Id: I7e0b9a18a308d5e9834a4a341d71192b37745b98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971047Reviewed-by:Shu Chen <shuchen@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#726156}
Showing
Please register or sign in to comment