Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
This protocol provides a subset of the wlr-foreign-toplevel-management
protocol. In particular this protocol provides a way for privileged clients to get a handle to a toplevel surface that may exist in another process and use the handle in other extension protocols.
This protocol is intentionally minimal as further information to describe a toplevel should be implemented with extension interfaces. For example, a protocol which may manage toplevels would use the handles defined in this protocol to reference the toplevel to set the state of. Another example use case is specifying a toplevel to capture the content of with a screencopy protocol.
An extension protocol to describe the state of a toplevel is being drafted here and uses this protocol: !196
Features provided in the wlr-foreign-toplevel-management
, and the proposed ext-workspace
protocols will be added in a future extension protocol and will use the handle type defined in this protocol.
From the past revisions of the protocol, the following has been done: