https://bugs.kde.org/show_bug.cgi?id=525847
--- Comment #1 from David Edmundson <[email protected]> --- You're right. TextInputV3 is a bit unusual when it comes to double-buffering. Client->kwin is like every other protocol: >Values set with this request are double-buffered. They will get applied on the >next xx_text_input_v3.commit request, and stay valid until the next committed >enable or disable request. kwin->client does say: Values set with this event are double-buffered. They must be applied and reset to initial on the next zwp_text_input_v3.done event. Values set with this event are double-buffered. They must be applied and reset on the next zwp_text_input_v3.done event. -- You are receiving this mail because: You are watching all bug changes.
