Do not send reset to an already active input context.
This may be problematic for certain client, e.g. firefox, and cause input always reset after any key press. Also, sending reset on an activate also does not match the text input v3 semantics.
This commit is contained in:
parent
bd40db7dd1
commit
0b1565c54c
1 changed files with 0 additions and 2 deletions
|
@ -140,8 +140,6 @@ void InputMethod::setActive(bool active)
|
||||||
|
|
||||||
if (!wasActive) {
|
if (!wasActive) {
|
||||||
waylandServer()->inputMethod()->sendActivate();
|
waylandServer()->inputMethod()->sendActivate();
|
||||||
} else {
|
|
||||||
waylandServer()->inputMethod()->context()->sendReset();
|
|
||||||
}
|
}
|
||||||
adoptInputMethodContext();
|
adoptInputMethodContext();
|
||||||
} else {
|
} else {
|
||||||
|
|
Loading…
Reference in a new issue