Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do updates to the edit control result in syncing state with the browser process too frequently? #7

Open
BoCupp-Microsoft opened this issue Feb 12, 2019 · 1 comment

Comments

@BoCupp-Microsoft
Copy link

RE: When the editing context is changed in edit control, a mojo message is sent to the browser process to update the TextInputState struct to stay in sync with the focused edit control.

What's the trigger for the mojo message? Transient state generally isn't interesting. As a principle I'm thinking the view we provide to Windows Text Services should be aligned with the view provided to the user (when we update the screen).

@siliu1
Copy link
Owner

siliu1 commented Feb 12, 2019

TextInputState struct is used for handling IME on the browser side. The TextInputState struct contains information such as type, mode, text in edit control, selection, etc. are used by the input method to handle IME. This struct is used across all platforms for IMEs.

We only run the diffing algorithm to update the view of Windows Text Services when there is a layout/view change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants