Context menus wrong position on multiple displays with mixed DPI

[PSzczepanski1996]

Tested on Terminator and Firefox, the same bug occurs in Gnome so I don't know where it happens, I heard that it's libgtk bug but probably not. I use Wayland build of Firefox of course, and scale 1.75 or 2 of my secondary 4K monitor.

If there is similar issue - sorry for posting it.

[PSzczepanski1996]

Also, in sway opening context menu near border causes bug where border is at higher index than context window, and that causes graphical defect.

See here:
https://imgur.com/a/pPg0vQA

[ammen99]

Just a tip, on most wlroots-based compositors (including Sway) you can use https://github.com/emersion/grim to create screenshots.

[PSzczepanski1996]

Just a tip, on most wlroots-based compositors (including Sway) you can use https://github.com/emersion/grim to create screenshots.

Yes I know but I had not hotkey attached and doing it via terminal was causing context menu dissapear so I though it will be faster to do with phone.

[RedSoxFan]

Tested on Terminator and Firefox, the same bug occurs in Gnome so I don't know where it happens, I heard that it's libgtk bug but probably not. I use Wayland build of Firefox of course, and scale 1.75 or 2 of my secondary 4K monitor.

I'm pretty sure this is related to swaywm/sway#3135 (comment).

For Firefox, see https://bugzilla.mozilla.org/show_bug.cgi?id=1423598. It looks like that was fixed within the past week and should be included in the recent nightly builds.

I'm not sure what the status is for Terminator.

Also, in sway opening context menu near border causes bug where border is at higher index than context window, and that causes graphical defect.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1528021, which was closed as a duplicate of the issue above and thus should also be resolved in recent nightly builds.