Re:I'm tired of this anti-Wayland horseshit
by roel_v on Tuesday February 02, 2021 @11:06AM
(#26002637)
If every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?
[ Parent
| on HN ]
Re:I'm tired of this anti-Wayland horseshit
by jyxent on Tuesday February 02, 2021 @01:05PM
(#26004345)
https://bugs.chromium.org/p/chromium/issues/detail?id=112178...
Chrome regressed on Wayland after changing the default rendering path on Linux. The slowness seems to be a problem in getting proper vsync, and there are multiple cases where it was/is causing issues.
Re:I'm tired of this anti-Wayland horseshit
by whatshisface on Tuesday February 02, 2021 @11:13AM
(#26002743)
Chrome has separate code for dealing with each compositor. The bug would be in the code that deals with Wayland specifically.
Re:I'm tired of this anti-Wayland horseshit
by kaba0 on Tuesday February 02, 2021 @03:07PM
(#26005900)
Chrome doesn’t even run on wayland, unless compiled specifically on a new enough branch so OP talks about the version running inside XWayland. It can possibly be a bug in the specific compositor’s xwayland implementation or even in chrome.
Also, your special ability to try out every compositors must be really useful.