ime: Ensure system PK code works ok when switching between VK/PK.
System PK and the VK extension share the same IME service and backend decoder. This shared state can make it brittle to swap between the two, especially since they use different APIs. Rather than handle all the edge cases carefully, we decided to opt for a more robust solution: - When the extension is enabled, all events are routed to the extension, including PK events. - When the extension is disabled, all events are routed to the system PK code. To ensure that the extension and system PK start with a clean state, we always reactivate the current engine (which would send an activate and focus event) when switching between the two. This guarantees that the extension and system PK are isolated from each other. Tested: on real device, flipping back and forth between clamshell/tablet. Bug: b/172771899 Change-Id: Ibef308a5b8798f5719da038d21320d11c689a3c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567013Reviewed-by:My Nguyen <myy@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#835097}
Showing
Please register or sign in to comment