https://bugs.kde.org/show_bug.cgi?id=489729

            Bug ID: 489729
           Summary: Bounce key delay doesn't seem to use the correct value
    Classification: Applications
           Product: systemsettings
           Version: 6.1.2
          Platform: Neon
                OS: Linux
            Status: REPORTED
          Keywords: accessibility, wayland
          Severity: minor
          Priority: NOR
         Component: kcm_accessibility
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY
Bounce key delay doesn't seem to use the correct value. When I set it to 100
(the lowest it seems to accept) I can mash a single key and it rejects quite a
few presses. There is no unit of measurement next to the value, but I assume
it's milliseconds. I would expect far fewer rejections for it to truly be set
to 100ms. The main reason I was looking into this is because I have a
mechanical keyboard that's chattering like crazy and discovered there's a
built-in feature to reject double-key presses. 

Additionally, I had a friend test this setting out and he can't even type
sentences without rejection. Something is definitely a bit off with the delay.

STEPS TO REPRODUCE
1. Navigate to System Settings > Accessibility > Keyboard Filters
2. Enable "Bounce Keys"
3. Adjust delay to 100 (Think default was 500?)
4. Ensure "Ring system bell when rejected" is enabled for easier debugging
5. Click Apply at the bottom right
6. Repeatedly mash a key as quickly as you can and wait for rejections.

OBSERVED RESULT
Far too many keys are rejected.

EXPECTED RESULT
I don't even think I can press a key 10 times in a second. I would expect a
much lower, if not null, rejection rate. Keys get rejection just from words
that have double letters.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 6.0
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-41-generic (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to