> My concern with adding cancellation behaviour is that there'll be no existing client or toolkit that expects it, and we can't make it opt-in (like the opt-in touch cancellation support).
That's a good point but extra events are kind of opt-in already with zero code change for most clients. If clients see an event they don't understand they should ignore it and not treat it as an error. On the other hand, cancellation support would help the VT switching problem with modifier press/release. And on the third hand ;) I continue to believe we should just be writing more robust code that can survive seeing a press without a release and a release without a press. Because clearly we have two real-world use cases (on phone and desktop!) where that can happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547864 Title: libinput doesn't handle EV_KEY event with a value of 255 (BUTTON_CANCLED), to support Android home buttons To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1547864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
