| Summary: | Notify user when the default application for something is changed | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Fernando M. Muniz <fernandommuniz> |
| Component: | kcm_filetypes | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CLOSED INTENTIONAL | ||
| Severity: | wishlist | CC: | faure, kdedev, nate |
| Priority: | NOR | Keywords: | privacy, usability |
| Version First Reported In: | 6.4.4 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Issue on Plasma 6.4.4 | ||
|
Description
Fernando M. Muniz
2025-08-09 05:55:03 UTC
Created attachment 183898 [details]
Issue on Plasma 6.4.4
Tell that to the people making the "Zen Browser", they must be the ones forcing their browser as having more priority. So this can't be stopped on KDE's end? No, I don't think so. Either they ship a .desktop file with a high InitialPreference key (that's the most likely scenario - this mechanism is based on people being reasonable...) or they edit ~/.config/mimeapps.list (I'm not sure how, though). Then can a notification be made for whenever a default app change? That would be the next best thing. Creating a notification when default app choices are switched may be something we can do. > The default apps should never change to the newest app without asking the user if that what they want.
That's a "be careful what you wish for" situation. There are cases where you do want the default app to change automatically. Some trivial ones I can think of are having an unsuitable app installed for a file type and then installing a suitable one, or having a suitable one installed and then installing a new one to test it out.
Notifying the user that this is happening every time would drive people slowly mad, I suspect. So I'm not sure we should do this, sorry.
Currently the user would have to guess which app changes the default and which doesn't. My suggestion could still work as an deactivatible setting. (In reply to Nate Graham from comment #7) > Notifying the user that this is happening every time would drive people > slowly mad, I suspect. So I'm not sure we should do this, sorry. Not even if deactivated by default? And by "drive people slowly mad" you mean a lot of apps change the defaults? Even more reason to have these notifications. What if that happens and you open private data with one of those apps (installed for other purposes) while expecting for it to be opened by the app you manually set as default? No, sorry. |