Closed Bug 1591936 Opened 6 years ago Closed 5 years ago

Select dropdown not showing options in multi monitor setup

Categories

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

72 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1597990
Tracking Status
firefox-esr68 --- disabled
firefox70 --- wontfix
firefox71 --- wontfix
firefox72 --- fix-optional
firefox73 --- unaffected

People

(Reporter: mozilla, Assigned: jhorak)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Attached file select.html

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

Steps to reproduce:

  1. Go to a page with a <select>
  2. Click it
<!DOCTYPE html><html><meta charset="utf-8"><body><select><option>a</option><option>b</option></select>

Actual results:

The list of options was not shown
(The select "buton" did become focued, that i there was a dashed border)

Expected results:

A list op options should be shown

This is on Wayland

OS: Unspecified → Linux
Hardware: Unspecified → x86_64

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Layout: Form Controls
Product: Firefox → Core

Works for me on wayland with Fedora 31, fwiw.

Blocks: wayland
Component: Layout: Form Controls → Widget: Gtk

I asked one of my coworkers with a very similar setup to me to reproduce this bug, but it did not reproduce.
I'll try to figure out why it breaks on my machine.

I can reproduce this (Arch Linux, WebRender, Wayland). I'll try mozregression tomorrow if nobody else does it.

Sorry, I can't actually reproduce this in mozregression, and in my old profile it's unreliable (sometimes works, sometimes doesn't, even without restarting the browser). I'm using Auto Tab Discard and session restore, but I still see no obvious link.

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression

I think I saw that with GL compositor + dmabuf backend enabled. I'll look at it.

Priority: -- → P3

I can no longer reproduce this bug in the latest Nightly.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME

Not fixed, I just saw it again in the 2019-11-06 Nightly. It's just hard to reproduce.

I'm using WebRender on Wayland without dmabuf.

I don't think this is a Firefox issue anymore, I have the same issue in some qt apps (I don't know what FF is using in the backend).

The drop down for some qt apps is moved to the side outside of the view (screenshot: https://imgur.com/a/zeCWE8U).
I think this might be related to my window manager (sway), but I'm not sure yet.

Firefox uses Gtk. It's a recent regression., but I didn't try mozregression yet because I'm still not sure if I can trigger it reliably.

Is has come and gone for me, at this moment I can repoproduce it (20191105-firefox-72.0a1.en-US.linux-x86_64)

Do you have two monitors? I'm on Gnome FWIW (I forgot to mention it before).

:stransky, do you think this is a good enough case to reopen the issue? I'll try mozregression later, but I can't promise I'll find anything from it.

Flags: needinfo?(stransky)

(In reply to Robbert Gurdeep Singh from comment #13)

Is has come and gone for me, at this moment I can reproduce it in 20191105-firefox-72.0a1.en-US.linux-x86_64.

Sorry, I mistyped, I cannot reproduce it in 20191105-firefox-72.0a1.en-US.linux-x86_64.

(In reply to Laurențiu Nicola from comment #14)

Do you have two monitors? I'm on Gnome FWIW (I forgot to mention it before).

:stransky, do you think this is a good enough case to reopen the issue? I'll try mozregression later, but I can't promise I'll find anything from it.

You may see a Bug 1593408 where the content is moved. But please reopen if you have any further info.

Flags: needinfo?(stransky)

I do see bug 1593408 happening, but it doesn't seem related to the issue at hand (drop-down pop-ups not drawing). Restating my comment above, I am able to reproduce the issue here, but I can't reopen it because I'm not the original reporter.

 4:13.37 INFO: Last good revision: e71fb039af065fbf81101c4c94ed48484242d2b1
 4:13.37 INFO: First bad revision: 48951378e166b2a1e84c923681b29e0c3e59a9fb
 4:13.37 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e71fb039af065fbf81101c4c94ed48484242d2b1&tochange=48951378e166b2a1e84c923681b29e0c3e59a9fb

Regressed by bug 1565401.

Status: RESOLVED → REOPENED
Regressed by: 1565401
Resolution: WORKSFORME → ---

I was going to do the same as :darkspirit, and there was an edit collision, I wrote the following:

I reopen this bug as Laurențiu Nicola seems to still face the issue and had put in the work to do a mozregression.

For me the problem seems to have disappeared without clear reason, but I have been messing with the gtk config (chaning themes and defaults), and parts of my window mananger.

I cannot reproduce this myself in the 2019-11-07 nightly.

More details: I was able to reproduce this on a dual-monitor system. I'm not sure if it happens with a single one. It only affects Wayland, and I tested with WebRender enabled. Without WR, I can't really tell what's happening, because everything is drawn in the wrong place.

Since you are speaking of dual monitor, I just realised that I have only seen this bug in a dual monitor setup (which I am currently not on). I will check again when I am in proximity of my other monitor.

I've been seeing this on Sway with native wayland for a few weeks.

I tested with an empty profile and can confirm it's related to multi monitor:

1st test run:

  • Browser launched with two display: bug present
  • Subsequently external monitor unplugged: bug still present

2nd run:

  • Browser launched with just one display: bug not present
  • Subsequently 2nd display plugged: bug present
  • Subsequently unplugged: bug not present

The problem indeed only manifest in dual monitor setup for me.

Contrary to ericdrex 1st test run, the problem is resolved for me when I unplug my external monitor.

(sway version 1.2, wlroots 0.8.1-1, Linux beardhatcode 5.3.8-arch1-1 #1 SMP PREEMPT @1572357769 x86_64 GNU/Linux)

This bug still affects me in 72.0a1 (2019-11-13) (64-bit) when in dual monitor setup.

In other GTK applications (and FF 71), dropdowns work correctly. (Some older Qt applications also fail)

Summary: Select drowpdown not showing options → Select dropdown not showing options in multi monitor setup

I'm affected by the same bug on Firefox 70.0.1-4.fc31 since today. The bug is present in all firefox profiles on a multi-monitor setup and not present with only one monitor. Connecting a monitor / disconnecting all additional monitors toggles the bug (restart of firefox is not necessary).

Stefan Pfeil, that's odd I do not see the issue on 70.0.1. From what version of Firefox did you update? Are you also running swaywm? What is your os?

Flags: needinfo?(pfeil)
See Also: → 1391627

I added a screenshot to clarify the issue and to show how it differs from bug 1391627

(In reply to Robbert Gurdeep Singh from comment #26)

Stefan Pfeil, that's odd I do not see the issue on 70.0.1. From what version of Firefox did you update? Are you also running swaywm? What is your os?

I'm running more or less a default installation of Fedora 31 (Workstation Edition) with Gnome version 3.34.1, upgraded from Fedora 30. I'm not running swaywm.

Recent Updates that may be relevant:
Most likely: firefox-70.0-1.fc31.x86_64 -> firefox-70.0.1-4.fc31.x86_64
On the day before: gtk2-2.24.32-5.fc31.x86_64 -> gtk2-2.24.32-6.fc31.x86_64

Neither in the ui nor on any webpages dropdowns are showing any options. It is the same behaviour as shown in the screenshot above. This is clearly not Bug 1391627.

Flags: needinfo?(pfeil)

This is the root bug on Fedora's bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1773715

Adding more and more duplicates as time goes by.

I have added the versions of things I can reproduce the issue with here (which I just closed as a duplicate of Fedora #1773715):
https://bugzilla.redhat.com/show_bug.cgi?id=1776934

In my scenario, restoring firefox to a non-maximised state does not fix the issue.

Any news on this as yet? It really does break the web having this issue. From banking to shopping to bug reporting - it cripples the web.

For what its worth, having 3 monitors, moving the window to a screen without the gnome taskbar does not give a workaround, nor does making sure the window is not maximised.

Jan, can you look at ti please?
Thanks.

Assignee: nobody → jhorak
Flags: needinfo?(jhorak)

It works for me in FF 73.0a1 (2019-12-04) (64-bit)
It does not work in FF 72

I'm marking this as fixed (as it is fixed in the 73 nightly for me)
Let me know if you still have issues with the nightly.

(Should I close this issue?)

Yeah, this time it seems to have been fixed.

If somebody could figure out what fixed it using mozregression it'd be pretty cool.

Looks like it's bug 1597990.

Well, that would make sense :)

Thanks for fixing this Jan!

Status: REOPENED → RESOLVED
Closed: 6 years ago5 years ago
Flags: needinfo?(jhorak)
Resolution: --- → DUPLICATE
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: