Bug 198944 - pressing enter on a button in a message box with a default button should not use the default
Summary: pressing enter on a button in a message box with a default button should not ...
Status: RESOLVED DUPLICATE of bug 190631
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.2
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-04 19:55 UTC by Shriramana Sharma
Modified: 2009-07-04 21:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shriramana Sharma 2009-07-04 19:55:52 UTC
Version:            (using KDE 4.2.2)
Installed from:    Ubuntu Packages

This is a kdelibs problem because it occurs independently but in the same way in KWrite/Kate/Kolourpaint.

Steps to reproduce:
1. Open one of these applications (or some other KDE 4 application that can create documents). 
2. Make some changes in an empty document or existing document. 
3. Attempt to exit without saving.

What is seen:
I get a dialog box giving options Save, Discard, Cancel. Here Save is the default button. If I use the keyboard to navigate to either Discard or Cancel and press Enter, the appropriate action i.e. either discarding or cancelling does not occur. Instead pressing Enter triggers the default button which is Save and hence I get a Save As dialog (or worse, unwanted changes are saved to an existing file). I have to press Space when focus is on Discard or Cancel to "press" that button from the keyboard.

What is expected:
The default status is given to a button only to indicate that it should be considered pressed when Enter is pressed anywhere in the dialog **when no button is having focus**. When a button is having focus, only that button must be considered pressed when Enter is pressed, not the default button.

Please fix this.
Comment 1 Michael Pyne 2009-07-04 21:24:06 UTC

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