GNOME Bugzilla – Bug 406543
Buttons should provide feedback when resisting clickability
Last modified: 2007-05-18 04:40:00 UTC
I have always thought this was a bug with Gnome: When something in the Window changes and you try to click a button, the button doesn't click. You have to move the cursor away from the button and back to it before it becomes clickable again. This annoyed me persistently. Then I realized that maybe it was meant to behave like that, to prevent accidentally clicking on things when a Window disappears, etc. I think this is a good idea, but the button should provide some sort of active feedback to indicate that it is resisting being clicked, instead of just not responding. Maybe if the edge of the button flashed red or something. I'm sure you can think of a better visual effect, but it needs something to say "I know that you clicked here, but I'm not going to accept it because it might have been accidental. I'll return to normal functionality if you move the cursor away and move it back again". Other information:
Better visual effect: A button can be considered "temporarily disabled" and would appear grayed out (maybe a distinct grayed out from normal). The grayed-out-ness would disappear as soon as the mouse cursor moves away from it.
Can anyone confirm that, in the first place, the "resisting clickability" is by design?
No, it is not. But you need to describe in some more detail a situation where a button does not react on a click for us to reproduce it.
(In reply to comment #3) > No, it is not. But you need to describe in some more detail a situation where a > button does not react on a click for us to reproduce it. I notice it most often in Synaptic because of the load time: 1. Start Synaptic package manager 2. While the program is loading, the menu bar will be grayed out. Put the mouse cursor over the Search button 3. After the program has completely loaded, try pressing the button 4. Now move the cursor away from the button and back again 5. Press the button
Ok, buttons becoming sensitive is a longstanding issue. *** This bug has been marked as a duplicate of 56070 ***