Bug 82121 - the "dont ask again" button on close (with multiple tabs open) doesnt remember what you click (eg "close current tab or close all")
Summary: the "dont ask again" button on close (with multiple tabs open) doesnt remembe...
Status: RESOLVED DUPLICATE of bug 90375
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-24 22:29 UTC by jos poortvliet
Modified: 2010-08-23 22:47 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 jos poortvliet 2004-05-24 22:29:48 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    Mandrake RPMs

My girlfriend was really confused with this one: she is used to close a tab with the normal close button, and then choosing "close current tab". after I explained the use of the "dont ask again" option (not knowing she didnt want to quit all tab, but instead just quit one tab), she apparently ticked the option, and then closed the current tab, believing (naturally!) the next time she used the close button on the windec, only one tab whould close. but the whole window with tabs disappeared... which wasnt really what she expected to happen.

And I think it should be changed. the wording should change into "always close all" or the behaviour should follow what you choose (except cancel, I guess). or maybe make it 2 options instead of one: "always close all" and "always close one".

btw my girlfriend whould choose the second option (just make "dont ask again" work...). but she didnt know about the special button to close the current tab... so I'd only change the wording.

thanks for the work!
Comment 1 jos poortvliet 2004-10-06 12:05:03 UTC
as it is mostly wording, I'd say please make a few minutes for this one?
Comment 2 FiNeX 2010-08-23 22:47:10 UTC

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