absolute positioning and other "missing features" of Wayland

[Simon Ser]

On Monday, February 22nd, 2021 at 11:44 AM, Carsten Haitzler <raster at rasterman.com> wrote:

> I also would want to avoid baking explicit absolute positioning into wayland
> protocol - be it as a core agreed to add-on to xdg-shell or even a "commonly
> supported extension". What I'd like it some better solution. For example - if
> an app wants to absolute position a window because it's doing a custom "my own
> notification popup" much like Chrome and Firefox now like to do in X11, then I'd
> prefer this be explicitly exposed as a "notification surface with requested
> screen location hints" and so the compositor can decide to do something more
> intelligent with it. I am sure this list of use cases will probably be
> extensive and also depend on the API in wine that is being wrapped and
> intercepted - the higher level it is, the more it knows about the intended use
> case.

I'd like to avoid making this general, if we go down this road. Make it
specific to the win32 API and wine. Wayland-native toolkits don't need
it.

Notifications popups are part of the desktop environment and clients
shouldn't try to display them directly.