By default, it shoves it into some parallel file system within the snap.
Oh did you forget to actually explicitly save it into the downloads directory? Yeah, you have no idea where it is now.
Oh and of course when the download file explorer widget opens up, you can't get the mouse focus. Probably because there's some security boundary between Firefox and the file system.
Usability of firefoxes vastly decreased as a result of snaps
Finally, well this isn't a big deal to me. Apparently a lot of the open source people don't like it because the Firefox nap is basically just a call. The internet pull down binary command that pulls a huge binary blob and they don't like this.
Snap has done such a disservice to open source software’s perceived quality.
I don't think I did anything to change that either.
> On Firefox 119 I thought I was losing my mental faculties (even more) since I kept losing track of the cursor for a whole day. Turns out that it’s a Windows “feature” where you hide the cursor when you start typing into some input box. Maybe this is a Firefox-wide regression on Linux though. Difficult to find other examples of it on Linux via Google.
Firefox hides the cursor while typing, but it should unhide as soon as it's moved (at least it does for me)
> - More fun than a problem: `firefox --version` spews a warning: `update.go:85: cannot change mount namespace according to change mount ...` > - My dear XCompose wasn’t respected because of course you have to copy it to inside some dang `/home/me/snap/common/utensils/computer-applicances/apps/Firefox` tree
Those should both be snap specific.
> - The keyboard just does not work sometimes. No other apps seem to have this problem. So it’s apparently not some idiotic “applications that use X work but under Wayland it doesn’t” (or vice versa). Does a restart help? No. Seemingly only a computer reboot.
I don't know about that one. Could be Ubuntu or snap, but it does not happen on Arch. Out of curiosity, are you running firefox through xwayland or native wayland? (It says so on the about:support page under "Window Protocol")