As I understand it, X11 has many inherent security concerns, including programs being able to read the contents of other windows and intercept keystrokes. Wayland addresses these concerns but at the moment breaks certain functions like screen readers, cursor warping, and the ability of a program to resize its own window.

I am curious as to how the display protocols of MacOS and Windows handle these situations differently. How does a program in those operating systems gain permission to read the contents of other windows, if at all? What is to be done in Wayland for these functions to be more seamless or are there inherent obstacles?

  • vrighter@discuss.tchncs.de
    link
    fedilink
    arrow-up
    4
    ·
    1 month ago

    except the portal keeps popping up whenever I touch my controller, and the remember option does not work. It pops up in the foreground anytime I even accidentallytouch my contoller’s touchpad. In home streaming is basically impossible for me rn.

    • Zamundaaa@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 month ago

      That’s not really a Wayland thing, that’s an (apparently badly implemented) attempt to bridge X11 apps to a permission system they were never written for.

    • ReversalHatchery@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      What controller? That does not seem to be a problem with the portal concept, but a pretty weird bug in the implementation of some part of it.