> I think specific reasons have been provided. My apologies for missing those. Please link me to the relevant comment, so that I may re-read it. > When you define a type in WebIDL as an enumeration, rejection is happening when the value passed to a method is not valid. To implement the ignore rule with enum + current WebIDL, implementors would be required to add 'screen' as a valid value but ignore it, thus putting burden to those User Agents that have no use of this value. And putting burden on developers to understand that 'screen' is a valid but ignored value... * If we go with constraints, then this enum value already exists as [DisplayCaptureSurfaceType.monitor](https://www.w3.org/TR/screen-capture/#idl-def-DisplayCaptureSurfaceType.monitor). Safari [already ignores this](https://jsfiddle.net/2zbwftug/2/), so you'd literally requires **0 lines of code**. (But do correct me if I've made a mistake. This has been known to happen.) * If we go with non-constraints, yes, UAs will need a minimum of **1 line of code** in the IDL file in order to recognize `'monitor'`. How many more lines of code would be needed to not do anything? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/184#issuecomment-1027240154 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Tuesday, 1 February 2022 20:08:05 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:56 UTC