I just got a new laptop and installed OpenSUSE 16.0, after having used 15.x for the past couple of years. I use both Firefox and Chrome browsers, each with a dozen different profiles. I noticed a difference in the “open file” behavior, and since it started in both browsers at the same time, I think it’s an operating system change.
In OpenSUSE 15.6, when opening a file to upload, the default location the first time after startup would be the home directory, after that it would be the previous location I uploaded from, regardless of which browser or profile. It seems OpenSUSE 15.6 uses one single storage place for the location. (In OpenSUSE 15.5 and before, each browser had its own location, but that was still shared between all profiles within that browser).
In OpenSUSE 16.0, the location seems to be profile specific. Each profile defaults to the last open location for that profile, regardless of whether it was in the same session or a previous session.
Does anyone know if I can get back to the previous behavior, where the file open dialog is essentially shared between all applications, rather than each application having their own history? It would fit my workflow better.
The hardware is irrelevant to this discussion. I don’t use Chrome, but for Firefox at least check about:config > widget.use-xdg-desktop-portal.file-picker as that will influence the behavior you observe. On my Leap 16 install it is set to “true”, which means it uses desktop integration. KDE Plasma itself remembers last-used directories per application, not globally. AFAIU, browsers can store last-used directories per profile inside the browser, on top of KDE’s behavior.
Thanks for those who responded. I found that changing the widget.use-xdg-desktop-portal.file-picker does not seem to be making any difference.
I have concluded that the behavior where every browser profile has it’s own “last file picker location”, independent of the other browsers and profiles, is probably the intended behavior, and that the “feature” I had in Leap 15.6 with one global “last file picker location” may have been a bug. So I am getting used to this behavior.