After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781631 - Key-repeat options should be in Keyboard component
Key-repeat options should be in Keyboard component
Status: RESOLVED DUPLICATE of bug 781245
Product: gnome-control-center
Classification: Core
Component: Universal Access
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-04-23 10:06 UTC by Leander Schröder
Modified: 2017-04-23 10:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Searching for 'repeat' in gnome-shell returns the Keyboard component of gnome-control-center (760.52 KB, image/png)
2017-04-23 10:06 UTC, Leander Schröder 		Details

Description Leander Schröder 2017-04-23 10:06:48 UTC 
Created attachment 350259 [details]
Searching for 'repeat' in gnome-shell returns the Keyboard component of gnome-control-center

By convention users expect the key-repeat options in the Keyboard component.
Having it in the keyboard section of the Universal Access component breaks user expectations and thus users have trouble finding the key-repeat option.

For the reasons presented above I propose that the option is moved back to the Keyboard component.

Furthermore searching for 'repeat' or 'key repeat' in the gnome-shell returns the Keyboard component.
However it does not contain anything on key-repeat.
More search terms for the key-repeat options should be added to make them more discoverable.

Please note that there has been a previous discussion about moving key-repeat from Keyboard to Universal Access: https://bugzilla.gnome.org/show_bug.cgi?id=757464.
Comment 1 Bastien Nocera 2017-04-23 10:55:15 UTC 
This was already fixed in development versions of gnome-control-center.

*** This bug has been marked as a duplicate of bug 781245 ***