News for hackers. Stuff that matters.
Re:Exposing the Wayland lie (2018) by solarkraft on Sunday February 10, 2019 @10:06AM (#19128025)
One complaint in this specific thread is that applications can't control the location of their surfaces (which is needed for things like drop-downs and tool tips), but then again sub-surfaces can be controlled by the parent surface. This specific problem does look solveable.
Re:Exposing the Wayland lie (2018) by makomk on Sunday February 10, 2019 @12:11PM (#19128667)
As I understand it from that bug report, the problem is that the Windows app doesn't have to provide any link between the menu or tooltip and the window it's from that's visible to Wine. So your solution basically boils down to modifying every Windows app out there to make it Wayland-compatible, potentially including a bunch of niche industry-specific or even company-specific ones.

There's a similar problem with implementing X on top of Wayland, and so XWayland has special powers that normal apps don't in order to be able to work. That's why running Wine as an X client under XWayland doesn't have this problem.