Wait, does this request make any sense? (Brandon?)
The described use case was wanting to hide the OSK on focus loss. But
surely you only want to hide the OSK when the text widget loses focus.
So implementing this may stop the OSK from staying on screen after an
app switch (assuming Unity8 does not SIGSTOP the app, in which case this
is more pointless). But it won't solve the OSK staying on screen after
you've finished entering text. That's the job of the input method's
toolkit backend to signal that the input field is finished.
If the only remaining purpose of this request is to hide the OSK on app
switch, is it really necessary? Surely it's the shell's job to
automatically hide the OSK on app switch... And surely if Unity8 is in
the habit of SIGSTOP'ing apps when they lose focus then Xmir acting on
loss of focus is impossible anyway. Because the Xmir process would be
frozen.
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1582471
Title:
Add focus/unfocus event passing for Xmir non-rootless mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1582471/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
