Firefox flatpak on flathub beta

[bam (Andrey)]

Yes it does. Sorry, on a second look the app actually shows up, it just without icon and many (null) lines present in the GNOME Software, but on Flathub site it’s OK.

[fmuellner (Florian Müllner)]

@joefidler

I was able to get a list of my installed extensions and update an extension from extensions.gnome.org

Yay!

A word of warning though: Updating an extension from extensions.gnome.org will update the files on disk, but not the loaded extension. You have to restart your session for the update to really take effect.

[toMeloos (Tom Verdaat)]

Anyone else experiencing this?

When I open a file and choose to save to disk it always defaults to the /run/usr/{UID}/doc/{ID} path inside the Flatpak container. I’ve seen more Flatpaks do this, which is quite unintuitive.

Why doesn’t it remember the last used path? I’ve checked about:config and browser.download.lastDir is also set to this /run/usr/{UID}/doc/{ID} path in stead of the actual path last used for saving a file. Any solution?

[vala]

@toMeloos

Anyone else experiencing this?

When I open a file and choose to save to disk it always defaults to the /run/usr/{UID}/doc/{ID} path inside the Flatpak container. I’ve seen more Flatpaks do this, which is quite unintuitive.

Yes.
Also for me it completely freezes the computer (restart needed) when zooming in or out in Google Maps.

[bam (Andrey)]

How to check if Wayland/VAAPI acceleration is actually used?

[joefidler]

@toMeloos

Anyone else experiencing this?

I see similar for print-to-file from a browser page. Default file destination is inside the container: /home/USER/.var/app/org.mozilla.firefox/cache/tmp. I have to overide this every time.

[omichalek]

@toMeloos

By the way the Flatpak version does not use Wayland yet. If you are running Wayland and want Firefox to make use of it you’ll have to run these two commands to enable it for now:

flatpak override --socket=wayland org.mozilla.firefox
flatpak override --env=GDK_BACKEND=wayland org.mozilla.firefox

and this should not hurt I guess

sudo flatpak override --nosocket=x11 org.mozilla.firefox

[mpphill2 (Matthew Phillips)]

about:support will tell you the truth.

I use all these tweaks:
layers.acceleration.force-enabled
gfx.canvas.azure.accelerated (you have to add this one yourself to equal true)
gfx.webrender.all
gfx.webrender.compositor
gfx.webrender.compositor.force-enabled
gfx.webrender.enabled
gfx.webrender.precache-shaders
gfx.webrender.quality.force-subpixel-aa-where-possible
media.hardware-video-decoding.force-enabled
media.ffmpeg.vaapi.enabled
media.ffmpeg.low-latency.enabled
webgl.force-enabled
webgl.all-angle-options
webgl.msaa-force
dom.webgpu.enabled (doesn’t work yet)

They all appear to be enabled according to about:support and nothing breaks for me.