| 2012-08-16 03:17:20 |
Edward Donovan |
bug |
|
|
added bug |
| 2012-08-16 03:40:05 |
Edward Donovan |
description |
Gtk3 buttons, when used from the keyboard, are executing their actions on press events, not waiting for release. (If this was a policy change, I haven't seen any notice of it. I'm guessing it wasn't?) It violates expectations on the muscle-memory level, I think, and can be seen in plenty of important cases.
To reproduce:
- Bring up (by any means, mouse or keyboard) a dialog provided by gtk3, like 'Restart' from the system menu, or 'Install Now' in update-manager, or 'Empty Trash?' from nautilus or the launcher.
- Hit Tab on the keyboard until you are over a pressable button. To be safe, choose 'Cancel' or other no-op. :)
- Press the spacebar, or Return, and hold it down.
The button will be redrawn as pressed, then the action will happen right away.
Expected result:
The button would redrawn as depressed, but not be activated until the key is released, which I think is the longtime and universal GUI convention. If you were to hit escape, it would abort. If you wait to consider rebooting/upgrading/deleting, the dialog would wait with you. This is what mouse actions do, and gtk2 widgets do, and what gtk3 widgets used to do, I believe.
This has been happening for some weeks in Quantal. (It took me a while to understand what I was seeing, and confirm it.) I tested this in the current Debian unstable and saw the same problem. I haven't tried any other gtk3 platforms. I haven't looked through the changelogs yet, but I will try to get a chance.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libgtk-3-0 3.5.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Wed Aug 15 22:38:41 2012
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to quantal on 2012-06-14 (62 days ago) |
Gtk3 buttons, when used from the keyboard, are executing their actions on press events, not waiting for release. (If this was a policy change, I haven't seen any notice of it. I'm guessing it wasn't?) It violates expectations on the muscle-memory level, I think, and can be seen in plenty of important cases.
To reproduce:
- Bring up (by any means, mouse or keyboard) a dialog provided by gtk3, like 'Restart' from the system menu, or 'Install Now' in update-manager, or 'Empty Trash?' from nautilus or the launcher.
- Hit Tab on the keyboard until you are over a pressable button. To be safe, choose 'Cancel' or other no-op. :)
- Press the spacebar, or Return, and hold it down.
The button will be redrawn as pressed, then the action will happen right away.
Expected result:
The button would redrawn as depressed, but not be activated until the key is released, which I think is the longtime and universal GUI convention. If you were to hit escape, it would abort. If you wait to consider rebooting/upgrading/deleting, the dialog would wait with you. This is what mouse actions do, and gtk2 widgets do, and what gtk3 widgets used to do, I believe.
This has been happening for some weeks in Quantal. (It took me a while to understand what I was seeing, and confirm it. I've tried pretty hard to find something already filed, but if it's there, it escaped me.) I tested this in the current Debian unstable and saw the same problem. I haven't tried any other gtk3 platforms. I haven't looked through the changelogs yet, but I will try to get a chance.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libgtk-3-0 3.5.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Wed Aug 15 22:38:41 2012
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to quantal on 2012-06-14 (62 days ago) |
|
| 2012-08-17 16:23:00 |
Edward Donovan |
description |
Gtk3 buttons, when used from the keyboard, are executing their actions on press events, not waiting for release. (If this was a policy change, I haven't seen any notice of it. I'm guessing it wasn't?) It violates expectations on the muscle-memory level, I think, and can be seen in plenty of important cases.
To reproduce:
- Bring up (by any means, mouse or keyboard) a dialog provided by gtk3, like 'Restart' from the system menu, or 'Install Now' in update-manager, or 'Empty Trash?' from nautilus or the launcher.
- Hit Tab on the keyboard until you are over a pressable button. To be safe, choose 'Cancel' or other no-op. :)
- Press the spacebar, or Return, and hold it down.
The button will be redrawn as pressed, then the action will happen right away.
Expected result:
The button would redrawn as depressed, but not be activated until the key is released, which I think is the longtime and universal GUI convention. If you were to hit escape, it would abort. If you wait to consider rebooting/upgrading/deleting, the dialog would wait with you. This is what mouse actions do, and gtk2 widgets do, and what gtk3 widgets used to do, I believe.
This has been happening for some weeks in Quantal. (It took me a while to understand what I was seeing, and confirm it. I've tried pretty hard to find something already filed, but if it's there, it escaped me.) I tested this in the current Debian unstable and saw the same problem. I haven't tried any other gtk3 platforms. I haven't looked through the changelogs yet, but I will try to get a chance.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libgtk-3-0 3.5.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Wed Aug 15 22:38:41 2012
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to quantal on 2012-06-14 (62 days ago) |
Gtk3 buttons, when used from the keyboard, are executing their actions on press events, not waiting for release. (If this was a policy change, I haven't seen any notice of it. I'm guessing it wasn't?) It violates expectations on the muscle-memory level, I think, and can be seen in plenty of important cases.
To reproduce:
- Bring up (by any means, mouse or keyboard) a dialog provided by gtk3, like 'Restart' from the system menu, or 'Install Now' in update-manager, or 'Empty Trash?' from nautilus or the launcher.
- Hit Tab on the keyboard until you are over a pressable button. To be safe, choose 'Cancel' or other no-op. :)
- Press the spacebar, and hold it down.
The button will be redrawn as pressed, then the action will happen right away.
Expected result:
The button would redrawn as depressed, but not be activated until the key is released, which I think is the longtime and universal GUI convention. If you were to hit escape, it would abort. If you wait to consider rebooting/upgrading/deleting, the dialog would wait with you. This is what mouse actions do, and gtk2 widgets do, and what gtk3 widgets used to do, I believe.
This has been happening for some weeks in Quantal. (It took me a while to understand what I was seeing, and confirm it. I've tried pretty hard to find something already filed, but if it's there, it escaped me.) I tested this in the current Debian unstable and saw the same problem. I haven't tried any other gtk3 platforms. I haven't looked through the changelogs yet, but I will try to get a chance.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libgtk-3-0 3.5.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Wed Aug 15 22:38:41 2012
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to quantal on 2012-06-14 (62 days ago) |
|
| 2012-09-16 01:23:13 |
Edward Donovan |
summary |
Gtk3 buttons activated from keyboard on press, not on release |
Gtk3 buttons activated from keyboard on press event; should be on release |
|
