you are viewing a single comment's thread
view the rest of the comments
[–] 27 points 7 months ago (4 children)

Wayland isn't the problem. Chrome just doesn't behave well with it. I haven't had any Wayland-related issues with Firefox.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 11 points 7 months ago* (3 children)

    Yeah, maybe it was just badly worded by me...

    most (if not all) Wayland issues I currently have are related to Chromium, and especially CEF/Electron applications that are based on older Chromium versions. Weren't trying to say that this is an inherent Wayland issue, considering most of the applications works as expected.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 7 months ago* (last edited 7 months ago) (2 children)

    Ah I see. I understand now! I thought you may have been one of the people that is still saying X11 is superior, even though Wayland is very usable now.

    Ive been hitting weird issues in Chrome too, and had to disable GPU compositing to fix them. Unfortunately I have to use Chrome at work - we're not allowed to use other browsers, as only Chrome has the endpoint security functionality they require (provided by Chrome Enterprise Premium). No other browsers have or can provide the same features.

  • source
  • parent
  • hideshow 2 child comments