Open
Bug 1513268
Opened 5 years ago
Updated 2 years ago
Wrong toolbar menu & tooltip positions when using firefox nightly on gnome / wayland with display scale factor 150%
Categories
(Core :: Widget: Gtk, defect, P5)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox66 | --- | affected |
People
(Reporter: mail, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce: Running firefox nightly on Arch / Gnome 3.30 with a scale factor of 150% on Wayland. Opened firefox, opened any menu (for example to access preferences or any of installed plugins). Actual results: Popup menu appeared in center of screen Expected results: Popup menu should have appeared next to the button I clicked to open the menu
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Confirmed on 66.a01 from Dec 12. Also toolbar buttons don't appear in the top left area. Interestingly, it does not give the same issue on 100%, 125% or 200% display scale factor (configured via Gnome display settings), only an issue on 150%.
Summary: Wrong toolbar menu & tooltip positions when using firefox nightly on wayland with scale factor → Wrong toolbar menu & tooltip positions when using firefox nightly on gnome / wayland with display scale factor 150%
Comment 3•5 years ago
|
||
I've tested this report on Ubuntu 18.04 using the latest Nightly, Beta and Fx release builds. However, I could not reproduce the issue. I will try to install Arch in order to reproduce. Please change if this is not the right component.
status-firefox66:
--- → affected
Component: Untriaged → Preferences
Updated•5 years ago
|
Component: Preferences → Widget: Gtk
Product: Firefox → Core
Comment 4•5 years ago
|
||
Priority: -- → P5
Comment 5•2 years ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•