Because that’s completely different type of beast?
To be clear, if a change needs to be made, it should also affect other portals, as an app bug can trigger this issue in those portals as well. However, I don’t think there is a chance this will be fixed (it wouldn’t make sense for other portals), and certainly not for a specific portal. Only handling window spam (i.e. displaying multiple portal windows at the same time) is reasonable.
If I’m not mistaken, notifications are not blocked; they are not displayed.
Notifications are either allowed or not allowed, it’s a switch. Whether it is blocked or not displayed, doesn’t the inability to display count as blocking?
Getting back to this topic, what I’ve always been saying is to allow the repeatedly popping-up hotkey binding window to be hidden. Add a switch, like with notifications, so users can have the power to stop a specific program from showing this window. It’s just adding a ‘Don’t ask again’ checkbox! What’s so difficult about that?
Emmanuele put a lot of time in explaining why GNOME wouldn’t change its behavior here. It’d be nice if you could accept that rather than keep trying to suggest a different approach, even though the issue here is an app.
There are an open issue on flatpak about blocking the use of portals and the lockdown portal (which is limited and reserved for implementations).
That’s the only way to get what you want, but it needs to be there first.
However, even if this is implemented generally for all portals, there will be probably no reason (all the reasons given above) for GNOME to expose a setting to block the use of the global shortcuts portal, as what you want is just an extra in the wait of an app fix.
I’m running into this with Mattermost Desktop (Electron) app now.
Surprisingly there seems to be no matching issue for Electron GitHub · Where software is built
Wondering who is supposed to fix this where now
It have to be fixed in Chromium, then Chromium version with fix included will be used by Electron, which then will have to be used by applications.
I also spent a lot of time explaining why, as a feature provider, Gnome should do more! If you are just too lazy to change it, then you might as well not provide this function at all! In my opinion, you are just shirking your responsibilities. Just like when faced with your boss’s demands, you always have ten thousand difficulties and reasons not to do it. I know that as a free user I can’t ask for anything, but why are you should’nt think about it? Instead of just looking for reasons and excuses? Your attitude makes me unable to see your passion for Gnome. If you don’t love it, why do you still want to do it?
And you never responded directly to why notifications can be turned off from Gnome? Isn’t it also called by the application and then displayed by Gnome? Since notifications can be blocked by Gnome to avoid excessive interruptions, why can’t add a “don’t pop up again” checkbox for shortcut key binding, it’s a active pop-up too, same as notifications?
Because notifications are very much different from the global shortcuts popup.
Notifications are used by applications to notify the user about its current state (like new mails, an update to an task, etc.). These can be send often by an app. And, importantly, they are just a message. If you choose to ignore them with the “Don’t disturb” switch, it will not alter the app.
The global shortcuts portal on the other hand is supposed to only show once, when new shortcuts should be registered. And they are an active request to the user to define a setting, i.e. which shortcuts to use for the app, even when the app is not focused. And what the result of this request is can alter the behavior of the app, unlike with notifications.
Anyways, with that, I think everything is said:
Chromium had a bug which made it show the shortcut portal too often. This was fixed by Chromium upstream and should arrive in an update soon. Since this was an application bug, there’s nothing to fix from the side of GNOME.
why can’t add a “don’t pop up again” checkbox for shortcut key binding,
This is already explain in above post.
I think it’s time to close this topic.