Indicator appears as a thin line on openSuse Tumbleweed
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: mconley, Assigned: stransky)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Originally reported by ra.ravi.rav in bug 1642799 comment 3:
KDE Plasma taskbar preview of the said window.
On Linux (openSuse Tumbleweed) using v80.0a1 the indicator widow appears as a thin line, like just window borders. It appears as separate entry in KDE Plasma's task manager. The size of this indicator increases horizontally when I select option to present a window.
Reporter | ||
Comment 1•4 years ago
|
||
Hey jhorak, do you know why this might be?
Comment 2•4 years ago
|
||
I've been seeing the same problem on Gentoo with KDE Plasma for quite some time.
Assignee | ||
Comment 3•4 years ago
|
||
That needs to be re-tested on mutter, please run on terminal:
$mutter --wayland --nested &
$WAYLAND_DISPLAY=wayland-1 MOZ_ENABLE_WAYLAND=1 ./firefox
and check if you see it too or it's KDE specific.
Reporter | ||
Comment 4•4 years ago
|
||
Redirecting to the original reporter.
Hey ra.ravi.rav, any chance you could try what stransky suggests in comment 3?
Assignee | ||
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Hey Mike, the issue I see is on X server. The steps mentioned are for Wayland.
Assignee | ||
Comment 7•4 years ago
|
||
I see the regression on Wayland only, X11 works fine for me on latest nightly.
Assignee | ||
Comment 8•4 years ago
|
||
(In reply to Martin Stránský [:stransky] from comment #7)
I see the regression on Wayland only, X11 works fine for me on latest nightly.
I see it now. But on X11 it's KDE specific, I don't see that on Gnome.
Assignee | ||
Comment 9•4 years ago
|
||
It's caused by CSD decorations added to widget size, we need to add CSD sizes to max/min widget sizes.
Assignee | ||
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
Comment 12•4 years ago
|
||
bugherder |
Comment 13•4 years ago
|
||
It was suggested that this change might be the cause of bug 1660500.
Description
•