Fix range checking for PP_CdmKeyStatus

ppapi/proxy/ppapi_messages.h

Index: ppapi/proxy/ppapi_messages.h
diff --git a/ppapi/proxy/ppapi_messages.h b/ppapi/proxy/ppapi_messages.h
index 968fe57bf3635f4fd9c2de9dbfcf432186eb6841..88974445a2a1e9cc88ba448075a278765e09aade 100644
--- a/ppapi/proxy/ppapi_messages.h
+++ b/ppapi/proxy/ppapi_messages.h
@@ -95,7 +95,7 @@ IPC_ENUM_TRAITS_MAX_VALUE(ppapi::TCPSocketVersion,
 IPC_ENUM_TRAITS(PP_AudioSampleRate)
 IPC_ENUM_TRAITS_MAX_VALUE(PP_BlendMode, PP_BLENDMODE_LAST)
 IPC_ENUM_TRAITS_MAX_VALUE(PP_CdmExceptionCode, PP_CDMEXCEPTIONCODE_OUTPUTERROR)
-IPC_ENUM_TRAITS_MAX_VALUE(PP_CdmKeyStatus, PP_CDMKEYSTATUS_STATUSPENDING)
+IPC_ENUM_TRAITS_MAX_VALUE(PP_CdmKeyStatus, PP_CDMKEYSTATUS_RELEASED)

[xhwang, 2016/11/19 01:27:51]

The fix lg but is still error prone. Can we have something like 

PP_CDMKEYSTATUS_MAX = PP_CDMKEYSTATUS_RELEASED

and use PP_CDMKEYSTATUS_MAX here?

This is the pattern we use for IPC, but doesn't seem like widely used for ppapi
messages.

[bbudge, 2016/11/19 01:58:11]

I think it's fine to add a PP_*_MAX value to a Pepper enum.

[dcheng, 2016/11/21 10:15:56]

Let's just add a _MAX value then =)

 IPC_ENUM_TRAITS_MAX_VALUE(PP_CdmMessageType, PP_CDMMESSAGETYPE_LICENSE_RELEASE)
 IPC_ENUM_TRAITS(PP_DeviceType_Dev)
 IPC_ENUM_TRAITS(PP_DecryptorStreamType)