https://bugs.freedesktop.org/show_bug.cgi?id=105222
Peter Hutterer <peter.hutte...@who-t.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |---
Status|RESOLVED |REOPENED
--- Comment #9 from Peter Hutterer <peter.hutte...@who-t.net> ---
thanks for the fix, it does show the problem a bit better. Main question now is
of course: can you make this trigger for normal sequences? e.g. hitting
backspace multiple times, typing mm or ll or any of the common sequences that
would cause a user to type fast enough? This is quite important to gauge
whether we'll have regressions.
What's the minimum debounce time you can get away with? I can get 23ms
press->release time but 38ms is the lowest for release->press. Together they
are still way above the 30ms that we have in that script measuring between
press and press. So I think the debounce may actually be viable after all.
Given the experience we had with wireless mice in the button debouncing code,
this should only be enabled for internal (serial bus?) keyboards. Probably only
on specific models known to have broken hardware.
> would you accept a patch to add keyboard debouncing along these lines?
I'll be honest, I'm not enthusiastic about it but depending how complex it is
and how well it fixes the issue, maybe. This is still a hardware bug and having
to work around this in software (and keeping that behaviour for the next
decade) doesn't exactly fill me with joy...
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
