Urgh. My immediate reaction is “that touchscreen shouldn't be emulating a keyboard, damnit”.
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). Could we quirk this in either libinput or Mir to not send key-down until we've got a confirmed key-up? -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
