On Tue, 2014-06-24 at 18:27 +0000, Zsombor Egri wrote: > I know, there are exceptions, and people don't always like everything these > frameworks provide, and we should address those people. Things like tapping > on a static area to close OSK is not something people would expect to have.
Maybe it's because I'm a developer, and I'm used to more than 25 years of using computers that have pop-up UI elements like menus, and similar, which the OSK design and implementation certainly falls into the family of, and I expect that tapping outside of the pop-up widget's area, and not into another widget which would result in the same pop-up in the same position, to close that pop-up. If I tapped on another text entry, I'd expect the keyboard to stay. If I tapped on background text or empty space, I'd expect it to close. I'd also expect to be able to select and copy that text that isn't an interactive widget, in some way, so that I can paste it into a text entry elsewhere, if necessary. I think the best way to solve all these issues, is to have an explicit close button, as well as having a tap anywhere outside the keyboard area result in its closure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234982 Title: Keyboard does not auto-hide when no longer needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1234982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs