From 46f46863b7b5ac8d9c5bcdb167b57ae803d064ac Mon Sep 17 00:00:00 2001
From: Simon Ser <contact@emersion.fr>
Date: Wed, 16 Jul 2025 20:58:36 +0200
Subject: [PATCH] color-representation-v1: add protocol error for invalid
 chroma location

Clients are allowed to send any value from the enum (unlike other
requests where only supported values are allowed), however clients
are not allowed to send out-of-enum values.

Signed-off-by: Simon Ser <contact@emersion.fr>
---
 staging/color-representation/color-representation-v1.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/staging/color-representation/color-representation-v1.xml b/staging/color-representation/color-representation-v1.xml
index 9131700..3256a9d 100644
--- a/staging/color-representation/color-representation-v1.xml
+++ b/staging/color-representation/color-representation-v1.xml
@@ -145,6 +145,8 @@
              summary="the pixel format and a set value are incompatible"/>
       <entry name="inert" value="4"
              summary="forbidden request on inert object"/>
+      <entry name="chroma_location" value="5"
+             summary="invalid chroma location"/>
     </enum>
 
     <request name="destroy" type="destructor">
@@ -412,6 +414,9 @@
         chroma samples, corresponding to Chroma420SampleLocType code points in
         H.273.
 
+        An invalid chroma location enum value raises the "chroma_location"
+        protocol error.
+
         A call to wl_surface.commit verifies that the pixel format and chroma
         location type in the committed surface contents are compatible, if
         contents exist. The "pixel_format" protocol error is raised otherwise.