Closed Bug 1466616 Opened 8 years ago Closed 7 years ago

[Wayland] Bad behaviour and Appearance with GNOME scaling 125%

Categories

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

defect

Tracking

()

RESOLVED DUPLICATE of bug 1543035
Tracking Status
firefox60 --- affected
firefox61 --- affected
firefox62 --- affected

People

(Reporter: hjmallon, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce: Use Firefox on Macbook 13" with Fedora 28 and Scaling set to 125% To do this you need to run gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" Actual results: Hamburger menu has mouse pointer in wrong position Address bar doesn't show text or cursor It's pretty much unusable Expected results: Everything works at the new scaling factor
Hi hjmallon, I want to test this but please add the exact steps that you are doing in order to be able to reproduce this issue. Also if it's possible please make a screen recording. You are able to reproduce this with the latest Nightly? Please download Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem.
Flags: needinfo?(hjmallon)
I have just tried Nightly and done some more testing. It only happens when using the "Firefox on Wayland" icon. I hadn't noticed that before, also it happens on all scale factors !=100%, i.e. 200% too.
Flags: needinfo?(hjmallon)
Unfortunately, I don't have the proper environment to test this but based on comment 2 I will mark this as New.
Status: UNCONFIRMED → NEW
Component: Untriaged → Widget: Gtk
Ever confirmed: true
Product: Firefox → Core
Summary: Bad behaviour and Appearance with GNOME scaling 125% → [Wayland] Bad behaviour and Appearance with GNOME scaling 125%
Version: 60 Branch → Trunk

Yes, I can see that.

This is most likely a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1543035 and fixed in gtk 3.24 master / 3.24.9

Priority: -- → P3

Okay, let's track it in Bug 1543035.

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.