https://bugs.kde.org/show_bug.cgi?id=492225
--- Comment #4 from orko <o...@igalia.com> --- @David Thanks for looking into this. > They must be applied and reset to initial on the next zwp_text_input_v3.done > event This is true. However, I was not sure when that is applicable, because the following doc from zwp_text_input_v3.done seems somewhat contradictory: > Instruct the application to apply changes to state requested by the > preedit_string, commit_string and delete_surrounding_text events So it was my interpretation that if there are no state changes explicitly requested by those events, there are no changes to be applied. I could be interpreting it wrong still, or perhaps there could be some further clarification in the protocol. > if a released Chrome relies on this behaviour Technically chrome does have an "experimental" option to enable text-input-v3 which does rely on this behavior, but it's still not an officially supported feature yet, and probably won't be until the key events are supported. However, users might be running into this until then. So I'm open to it being addressed in either chrome or KDE. -- You are receiving this mail because: You are watching all bug changes.
