• dan@upvote.au
    link
    fedilink
    arrow-up
    17
    ·
    2 hours ago

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

    • SavvyBeardedFish@reddthat.com
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      2 hours ago

      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.

      • dan@upvote.au
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 hours ago

        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 composting 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.