Bug 504141

Summary: "Do not ask again" is ambigious in its scope (is it per file or per action type?)
Product: [Frameworks and Libraries] frameworks-kio Reporter: tomashnyk
Component: Open/save dialogsAssignee: KIO Bugs <kio-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: kde, kdelibs-bugs-null, nate
Priority: NOR Keywords: usability
Version First Reported In: git master   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: https://invent.kde.org/frameworks/kio/-/commit/9f709dc38d569203aaaa1a0c6d4ae685a9b27184 Version Fixed/Implemented In: 6.15
Sentry Crash Report:

Description tomashnyk 2025-05-13 09:05:38 UTC 
Regarding the recent work on https://blog.broulik.de/2025/05/kio-goodies (thanks for it!), I would like to point out the "Do not ask again" checkbox is ambigious. It is not clear to me as a user whether when checked, I won't be asked again about that specific file or if I will never be asked that question again for any file.

If the former, the text should be "Do not ask again for this file".

If the former, the text should  be "Do not ask again for all files".

Both are longer, but it seems there is enough place in the dialog at least in English (not sure about other languages). However, as of now, I never use this checkbox because I do not know what it will do.

Additionally, if this is not per file, maybe it should be per file (or both). To me, setting this per file is a lot more useful, because with different files, I want different default action. This is also somewhat related to https://bugs.kde.org/show_bug.cgi?id=190238 which also makes me try to avoid checking the "Do not ask again" checkbox. However, I do not at all call for removing the checkbox, I think it is useful to a lot of people.

This applies at least to these two dialogs (called ExecutableFileOpenDialog ):

https://blog.broulik.de/wp-content/uploads/2025/05/Screenshot_20250512_162135.png
https://blog.broulik.de/wp-content/uploads/2025/05/Screenshot_20250512_162152.png
Comment 1 Nate Graham 2025-05-13 22:00:32 UTC 
Agreed. The scope being unclear here makes it a potentially dangerous setting, I'd even say.
Comment 2 tomashnyk 2025-05-17 09:31:44 UTC 
Looks like this was just solved, no? https://invent.kde.org/frameworks/kio/-/merge_requests/1893

That was quick, thanks!
Comment 3 Nate Graham 2025-05-17 13:22:25 UTC 
Yep!