Closed Bug 1678345 Opened 4 years ago Closed 4 years ago

[Flatpak] [Wayland] Extension contents don't show up

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 83
Desktop
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1672139
Tracking Status
firefox83 --- affected

People

(Reporter: theevilskeleton, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

Using Firefox in a Wayland window.

I tried to open an extension, expected its contents to show up.

Actual results:

The extension's contents are completely blank.

Expected results:

It should show the contents of the extension.

Summary: [Flatpak] Extension contents don't show up → [Flatpak] [Wayland] Extension contents don't show up

After installing Fedora (which uses Wayland by default) in Virtual Box, downloading Firefox Release v83.0, installing the uBlock Origin extension (the only one I could recognize), this issue would not reproduce, nor would it with many other random installed extensions.

@theevilskely@tutanota.com: I will try to find a proper installation of Fedora to be tested as well, but in the meantime, please give me some more information:

  1. What operating system did you reproduce this issue on?
  2. If it isn't a Fedora, how did you open a Wayland window?
  3. What are the other extensions that you used in the issue's reproduction demo?

Thank you!

Component: Untriaged → Widget: Gtk
Flags: needinfo?(theevilskely)
Flags: needinfo?(daniel.bodea)
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → Desktop
Priority: -- → P3

Martin: bug 1677361 coment c9 might be related here.

Thanks for the report!
WebRender on MOZ_ENABLE_WAYLAND=1 is broken in Firefox 83: All addon panels are empty most of the time. :/
It will be fixed with Firefox 84 (currently Beta).

You can either disable gfx.webrender.all on about:config, or start Firefox without MOZ_ENABLE_WAYLAND=1 and GDK_BACKEND=wayland env vars.

No longer blocks: flatpak
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(theevilskely)
Flags: needinfo?(daniel.bodea)
Resolution: --- → DUPLICATE

(In reply to Bodea Daniel [:danibodea] from comment #1)

After installing Fedora (which uses Wayland by default) in Virtual Box, downloading Firefox Release v83.0, installing the uBlock Origin extension (the only one I could recognize), this issue would not reproduce, nor would it with many other random installed extensions.

@theevilskely@tutanota.com: I will try to find a proper installation of Fedora to be tested as well, but in the meantime, please give me some more information:

  1. What operating system did you reproduce this issue on?
  2. If it isn't a Fedora, how did you open a Wayland window?
  3. What are the other extensions that you used in the issue's reproduction demo?

Thank you!

I was using Fedora.

By default, Firefox opens an X11 window, despite being in a Wayland section (see about:support -> Window Protocol, it will say x11).

So you will need to run with the MOZ_ENABLE_WAYLAND=1 environment variable: flatpak run org.mozilla.firefox --env=MOZ_ENABLE_WAYLAND=1, and it should launch it in a pure Wayland window.


Anyway, using the beta version fixes it, so I started using it.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: