How Can I Double Click to Upload Files?

So the double click originally worked after you switched from your system integration support.mozilla.org/en-US/questions/1575323 and only ceased working after this change?

Or you don't have an exact time frame so it could have been connected to opting out of the XDG provider?

widget.use-xdg-desktop-portal.file-picker (default: 2) Whether to use gtk portal for the file picker.

- 0: never
- 1: always
- 2: auto (true for flatpak or GTK_USE_PORTAL=1, false otherwise)

If 0 vs. 2 differ for you, it means you're either using a flatpak version, or overriding the file pickers in your env. So the double–click actually works in the default setup, and you only need to resolve support.mozilla.org/en-US/questions/1575323 which I'd normally attribute to a bug/change in e.g. your xdg provider, but since the previous thread mentions resolving the recent folder by downgrading, it could be actually tracked down with bisection. You can run mozilla.github.io/mozregression between v148–v149 on your system to help inform when the recent folder stopped being remembered with your gtk/xdg setup.

Hello. No, the double click was working, up until my computer upgraded to a new version of Firefox just a few days ago. Before that, double clicking, and my last upload location, were both working together. I think it has something to do with the new Firefox version.

Hey Ryan, in that case please use the mozregression linked above to help find the changeset responsible. There were similar reports that using Enter key no longer works in similar fashion — hinting at the file picker not understanding what its default action is, but given this is explicitly non–standard setting for your environment, you might wanna file that in bugzilla to see if it gets some traction, or depends on any known issue. There are folks familiar with Gtk widgets and any recent changes so that's the avenue to pursue.

Can you give me some more information on what I'm exactly supposed to do with the program? I've managed to download and launch it, but I have no idea what I'm supposed to do with it. I watched the tutorial video on the website, but its not super clear, and I'm still confused as to what to do, and what information you might need from me to fix the bug. Thanks.

You tell it a range of versions, it will run one by one, you try the feature you're considering regressed at some point, and you click "good" or "bad" — that will repeat as the run narrows the regression window — and once you're done you'll just copy or screenshot the resulting log.

(I'll check the version in the threads and will post some hints separately in a bit…)

This is an example result:

I'd start with the "last file upload location" issue to verify it's an environment impact rather than code change, but in case that one leads to something, there'd be no need to tinker with portals' preference and this later issue would also go away.

So that's using defaults and just a range of versions. I'm attaching some notes what to set.

It will download and launch version after version based on your assessment whether the feature you're testing works as expected or not — and after you try the interaction you're investigating in given build you just close it, return to the mozregression, and tell it good vs. bad (the UI has colored buttons on the build line) and it will get another copy.

If none of the versions change that behavior, i.e. you're unable to track any regression in that range window, it's coming from the system, and not a change in the app. If you're seeing good vs. bad builds, it means it's most likely coming from a changeset and the app will be narrowing the window down with your ongoing results.