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 148208 - In the Keyboard Shortcuts capplet, the "hint" area should not be resizeable
In the Keyboard Shortcuts capplet, the "hint" area should not be resizeable
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
unspecified
Other Linux
: Normal trivial
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 140394 144167 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-07-22 20:31 UTC by Vincent Noel
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot showing a resized hint area (33.73 KB, image/jpeg)
2004-07-22 20:32 UTC, Vincent Noel 		  Details
Expand to false to the hbox (671 bytes, patch)
2004-07-23 16:47 UTC, David Sedeño Fernández 		accepted-commit_now Details | Review

Description Vincent Noel 2004-07-22 20:31:14 UTC 
Description of Problem:
When you resize the Keyboard Shortcuts capplet,
the "hint" area (with the lightbulb) resizes as
well. It should not. It looks strange when the
window size is big enough (see screenshot)
Comment 1 Vincent Noel 2004-07-22 20:32:03 UTC 
Created attachment 29803 [details]
screenshot showing a resized hint area
Comment 2 David Sedeño Fernández 2004-07-23 16:47:49 UTC 
Created attachment 29832 [details] [review]
Expand to false to the hbox
Comment 3 Jody Goldberg 2004-07-23 19:51:41 UTC 
Comment on attachment 29832 [details] [review]
Expand to false to the hbox

please apply.
Comment 4 David Sedeño Fernández 2004-07-23 20:18:46 UTC 
Committed to HEAD
Comment 5 Vincent Noel 2004-08-05 16:40:57 UTC 
*** Bug 140394 has been marked as a duplicate of this bug. ***
Comment 6 Vincent Noel 2004-08-05 16:42:10 UTC 
*** Bug 144167 has been marked as a duplicate of this bug. ***