[RFC wayland] protocol: Add wl_surface.buffer_damage

[Daniel Stone]

On 6 November 2015 at 19:08, Jasper St. Pierre <jstpierre at mecheye.net> wrote:
> To help clear things up, I think we should deprecate the
> wl_surface.damage request and document that the coordinates are
> effectively undefined -- for legacy reasons, if you see
> wl_surface.damage, it should be considered a damage for the entire
> surface.

Why? Mesa fixed that bug two years ago, I don't know of a non-Mesa EGL
implementation with that bug, and non-EGL clients are perfectly
capable of implementing it correctly themselves. Whilst introducing
buffer_damage, we could obliterate surface damage out of spite, but
that seems like a giant middle finger to everyone who wrote conformant
and performant apps, and now gets their entire buffer smashed through
TexImage2D every time they want to blink a cursor.

Cheers,
Daniel