Skip to content

lifecycle of presentation_feedback and surfaces

The protocol description is not clear whether a compositor is required to send "discarded" events when a surface is destroyed (within a roundtrip).

If it is not guaranteed then clients will have to do their own bookkeeping of outstanding feedbacks.

Currently compositors behave differently.

This came up in the context of mpv: https://github.com/mpv-player/mpv/pull/11072

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information