Bug 100166 - Default answer for "destructive operation" confirming requesters
Summary: Default answer for "destructive operation" confirming requesters
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdeui (show other bugs)
Version: SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 195626 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-24 15:15 UTC by Marcin Orlowski
Modified: 2023-05-12 09:42 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Orlowski 2005-02-24 15:15:52 UTC
Version:           0.9.2 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8)
OS:                Linux (i686) release 2.6.10

IMHO all the requesters asking use for confirmation for destructive operations (like removing contacts etc) shall set "Cancel" as defalt answer, to avoid problems user accidentally hit ENTER when requester popups. I'd bet all good UI design guides shall raise that issue as well.
Comment 1 Olivier Goffart 2005-03-15 23:11:54 UTC
I've added the KMessageBox::Dangerous flag to all theses MessageBox, but that still doesn't work.

Now, it's up to kmessageBox to handle the Dangerous flag correctly.

But I'm not sure pressing enter to cancel the dialog the good thing, in a usability point of view.
Comment 2 s.v.savenko 2010-01-15 21:31:56 UTC
I hope it is never going to be changed. The dialog is already there as a safety measure.
Comment 3 Andrew Crouthamel 2018-11-02 22:56:38 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-16 05:36:40 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-13 02:54:04 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-28 05:23:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-01-12 05:16:07 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 8 Zayed Al-Saidi 2023-05-12 09:42:00 UTC
*** Bug 195626 has been marked as a duplicate of this bug. ***