wayland compositor does not receive gtk reset signal
GTK applications calls gtk_im_context_reset() with mouse clicks but gtk_im_context_wayland_reset() just sets ZWP_TEXT_INPUT_V3_CHANGE_CAUSE_OTHER and calls zwp_text_input_v3_commit() but the purpose of the API is the commit-text but not the reset.
Mutter receives the commit-text from mutter/src/wayland/meta-wayland-text-input.c:text_input_commit_state() but it cannot know the reset signals with the mouse clicks and cannot call clutter_input_method_reset().
The reset signal is used to commit the Hangul preedit text in the old cursor posigion and move the cursor to the new position or new application.
I guess gtk/text-input-unstable-v3-client-protocol.h needs additional API to send reset or GTK sends mouse events to mutter?