Closed Bug 1768820 Opened 2 years ago Closed 2 years ago

Wayland: Overlays not disappearing

Categories

(Core :: Widget: Gtk, defect)

Firefox 100
defect

Tracking

()

RESOLVED DUPLICATE of bug 1752678

People

(Reporter: getreideernt, Unassigned)

Details

Attachments

(1 file)

Attached image bugreport.png

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

Steps to reproduce:

  1. Open Firefox on wayland
  2. Go to a page which renders a overlay (examples: log in to website and firefox suggests a login, hover over an option and the website displays a tooltip, firefox asking if the login should be saved)

Actual results:

The overlay does not disappear anymore, even when clicking on the key icon for the "save password" case. Screenshot attached as file

Expected results:

The overlays should disappear as soon as they are clicked away.

NOTE (by submitter): in Screenshot: The overlay is still displayed after the login form and stays for all page loads. It only disappears after restarting firefox.

NOTE 2 (also by submitter): The user Agent shows X11, but I am running Wayland --> this is XWAYLAND. However, this does not occur on plain xorg.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

You sure this is XWayland? Can you attach the about:support information? This looks like bug 1752678, which is caused by toggling an experimental pref (gfx.webrender.compositor.force-enabled).

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(getreideernt)
Resolution: --- → FIXED

Err, I was going to close as dup, but then read comment 2. Didn't intend to close sorry.

Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: FIXED → ---

(In reply to Emilio Cobos Álvarez (:emilio) from comment #4)

You sure this is XWayland? Can you attach the about:support information? This looks like bug 1752678, which is caused by toggling an experimental pref (gfx.webrender.compositor.force-enabled).

I just tried that, and the problem disappeared. Thanks!

Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Flags: needinfo?(getreideernt)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: