Drop-down position bug in Weston
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm happy tu use Weston - a very simple desktop.
However many apps still use X, so I need Xwayland for compatibility.
Among the X apps, I have noticed an annoying bug. It goes like this:
bring up a dropdown menu. Move the window. Bring up the dropdown menu again, it has not moved with the window, it still appears at it's old location!
It will remain there - until I resize the window or until some internal event causes it's position to be recalculated.
It affects many apps (among them Chromium and Firefox). It also affects the contextual menu, drop-downs (autocomplete, etc.) and drag-and-drop areas. I have also observed it when using "sway" window manager instead of "weston".
Sublime Text and a bunch of other X apps seem to be immune. So I guess it is related to the toolkit or particular features that such apps use.
I have never observed this bug in any "native" Wayland apps.
Here is the thing:
I tried GNOME/Wayland and KDE/Wayland and didn't see that bug over there! Firefox, Chromium, it all works well over there!
At the moment I'm investigating, and have gathered some notes
(https://gist.github.com/rolfen/c57e4606856f900c654fabb5cf9a34b6)
I have built the latest version for Weston and Xwayland from source. Same.
I'm wondering if anyone knowledgeable in how these apps and window managers are assembled could help me draw some conclusions.
desktop-environment wayland bugs
asked Feb 7 at 18:03
Rolf
11610
add a comment |Â
up vote
0
down vote
favorite
I'm happy tu use Weston - a very simple desktop.
However many apps still use X, so I need Xwayland for compatibility.
Among the X apps, I have noticed an annoying bug. It goes like this:
bring up a dropdown menu. Move the window. Bring up the dropdown menu again, it has not moved with the window, it still appears at it's old location!
It will remain there - until I resize the window or until some internal event causes it's position to be recalculated.
It affects many apps (among them Chromium and Firefox). It also affects the contextual menu, drop-downs (autocomplete, etc.) and drag-and-drop areas. I have also observed it when using "sway" window manager instead of "weston".
Sublime Text and a bunch of other X apps seem to be immune. So I guess it is related to the toolkit or particular features that such apps use.
I have never observed this bug in any "native" Wayland apps.
Here is the thing:
I tried GNOME/Wayland and KDE/Wayland and didn't see that bug over there! Firefox, Chromium, it all works well over there!
At the moment I'm investigating, and have gathered some notes
(https://gist.github.com/rolfen/c57e4606856f900c654fabb5cf9a34b6)
I have built the latest version for Weston and Xwayland from source. Same.
I'm wondering if anyone knowledgeable in how these apps and window managers are assembled could help me draw some conclusions.
desktop-environment wayland bugs
asked Feb 7 at 18:03
Rolf
11610
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm happy tu use Weston - a very simple desktop.
However many apps still use X, so I need Xwayland for compatibility.
Among the X apps, I have noticed an annoying bug. It goes like this:
bring up a dropdown menu. Move the window. Bring up the dropdown menu again, it has not moved with the window, it still appears at it's old location!
It will remain there - until I resize the window or until some internal event causes it's position to be recalculated.
It affects many apps (among them Chromium and Firefox). It also affects the contextual menu, drop-downs (autocomplete, etc.) and drag-and-drop areas. I have also observed it when using "sway" window manager instead of "weston".
Sublime Text and a bunch of other X apps seem to be immune. So I guess it is related to the toolkit or particular features that such apps use.
I have never observed this bug in any "native" Wayland apps.
Here is the thing:
I tried GNOME/Wayland and KDE/Wayland and didn't see that bug over there! Firefox, Chromium, it all works well over there!
At the moment I'm investigating, and have gathered some notes
(https://gist.github.com/rolfen/c57e4606856f900c654fabb5cf9a34b6)
I have built the latest version for Weston and Xwayland from source. Same.
I'm wondering if anyone knowledgeable in how these apps and window managers are assembled could help me draw some conclusions.
desktop-environment wayland bugs
asked Feb 7 at 18:03
Rolf
11610
I'm happy tu use Weston - a very simple desktop.
However many apps still use X, so I need Xwayland for compatibility.
Among the X apps, I have noticed an annoying bug. It goes like this:
bring up a dropdown menu. Move the window. Bring up the dropdown menu again, it has not moved with the window, it still appears at it's old location!
It will remain there - until I resize the window or until some internal event causes it's position to be recalculated.
It affects many apps (among them Chromium and Firefox). It also affects the contextual menu, drop-downs (autocomplete, etc.) and drag-and-drop areas. I have also observed it when using "sway" window manager instead of "weston".
Sublime Text and a bunch of other X apps seem to be immune. So I guess it is related to the toolkit or particular features that such apps use.
I have never observed this bug in any "native" Wayland apps.
Here is the thing:
I tried GNOME/Wayland and KDE/Wayland and didn't see that bug over there! Firefox, Chromium, it all works well over there!
At the moment I'm investigating, and have gathered some notes
(https://gist.github.com/rolfen/c57e4606856f900c654fabb5cf9a34b6)
I have built the latest version for Weston and Xwayland from source. Same.
I'm wondering if anyone knowledgeable in how these apps and window managers are assembled could help me draw some conclusions.
desktop-environment wayland bugs
asked Feb 7 at 18:03
Rolf
11610
edited Mar 1 at 21:20
asked Feb 7 at 18:03
Rolf
11610
asked Feb 7 at 18:03
Rolf
11610
asked Feb 7 at 18:03
Rolf
11610
11610
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422608%2fdrop-down-position-bug-in-weston%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password