Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
If you don't have xdg-desktop-portal, and file dialogs don't show up for firefox, edit this on about:config
Posted 01-17-2024 at 01:57 PM by the dsc
Tags bug/feature, firefox, xdg-desktop-portal
on about:config there are four or five "xdg" related options. As the wonderful Arch-linux wiki explains:
So in my case, both with the default "2" and switching to "1" as a random attempt to fix things, nothing changed, file dialogs wouldn't show up. Whether that was Debian's package or Mozilla's tarball, althogh the latter also had additional GUI-compositor-related problems on its default profile, which I somehow solved or reduced in my custom profile.
But with "0" that works, at least with Debian's package and my custom profile, I removed the one from the tarball without testing, as I tried it as a solution for this problem to begin with.
Maybe I should someday take a look on how this XDG-portal thing works, perhaps I can setup it so that I can have some environment variable to toggle the desired file dialog as I launch a browser instance, rather than being a broader user-session-wide thing as it seems to be. Or maybe I should surrender to the XDG-desktop-portal standard and learn to code and fix whatever there's wrong with the QT/KDE one(s). Or maybe I should infiltrate GTK and somehow destroy it from the inside so everyone has to use only QT, so maybe I don't have to fix the QT/KDE bugs myself. The sabotage route is probably much harder to accomplish, though. Although it seems like more fun and a greater good to humankind, ultimately it's not as feasible.
Quote:
Each setting can have the following values:
0 – Never
1 – Always
2 – Auto (typically depends on whether Firefox is run from within Flatpak or whether the GDK_DEBUG=portals environment is set)
The settings are:
widget.use-xdg-desktop-portal.file-picker – Whether to use XDG portal for the file picker
widget.use-xdg-desktop-portal.mime-handler – Whether to use XDG portal for the mime handler
widget.use-xdg-desktop-portal.settings – Whether to try to use XDG portal for settings/look-and-feel information
widget.use-xdg-desktop-portal.location – Whether to use XDG portal for geolocation
widget.use-xdg-desktop-portal.open-uri – Whether to use XDG portal for opening to a file
https://wiki.archlinux.org/title/fir...al_integration
0 – Never
1 – Always
2 – Auto (typically depends on whether Firefox is run from within Flatpak or whether the GDK_DEBUG=portals environment is set)
The settings are:
widget.use-xdg-desktop-portal.file-picker – Whether to use XDG portal for the file picker
widget.use-xdg-desktop-portal.mime-handler – Whether to use XDG portal for the mime handler
widget.use-xdg-desktop-portal.settings – Whether to try to use XDG portal for settings/look-and-feel information
widget.use-xdg-desktop-portal.location – Whether to use XDG portal for geolocation
widget.use-xdg-desktop-portal.open-uri – Whether to use XDG portal for opening to a file
https://wiki.archlinux.org/title/fir...al_integration
But with "0" that works, at least with Debian's package and my custom profile, I removed the one from the tarball without testing, as I tried it as a solution for this problem to begin with.
Maybe I should someday take a look on how this XDG-portal thing works, perhaps I can setup it so that I can have some environment variable to toggle the desired file dialog as I launch a browser instance, rather than being a broader user-session-wide thing as it seems to be. Or maybe I should surrender to the XDG-desktop-portal standard and learn to code and fix whatever there's wrong with the QT/KDE one(s). Or maybe I should infiltrate GTK and somehow destroy it from the inside so everyone has to use only QT, so maybe I don't have to fix the QT/KDE bugs myself. The sabotage route is probably much harder to accomplish, though. Although it seems like more fun and a greater good to humankind, ultimately it's not as feasible.
Total Comments 1
Comments
-
... aparently you can't simply edit the shortcut keys to custom ones. You got used to "ctrl+shift+n" to open an incognito window, bad luck, either go back to a different browser, or get used to ctrl+shift+p"
Not as bad as nano's ctrl+w default for "find" and getting used to it and closing windows accidentally, but at least that can be edited.Posted 01-17-2024 at 02:10 PM by the dsc 
