activateContext only provides access to the keyboard for the dbus connection that requested it, so even if the keyboard wasn't dismissed (which it should be), no other application would gain access without first requesting that they be made the activate context (and so being subject to a focus check)
activateContext only provides access to the keyboard for the dbus connection that requested it, so even if the keyboard wasn't dismissed (which it should be), no other application would gain access without first requesting that they be made the activate context (and so being subject to a focus check)