- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 May 2023 13:58:26 +0000
- To: public-webrtc-logs@w3.org
The history here is that settings, capabilities, and constraints originally all used the same single WebIDL dictionary, [MediaTrackConstraintSet](https://w3c.github.io/mediacapture-main/#dom-mediatrackconstraintset). This made sense from a spec economy pov, since you can express both settings and capabilities as constraints. I.e. settings and capabilities are subsets of constraints (and also valid arguments to constraints, even today).
But then we realized this was a parsing nightmare for JS, since no guarantees were given in prose about how a value would be returned, e.g. in getCapabilities().
JS would _in theory_ have to be ready for a user agent to return e.g. `{channelCount: 1` or `{channelCount: [1]}` or `{channelCount: {exact:1}` or `{channelCount: {exact: [1]}`. And that this was terrible for web compat.
It was when making this transition to tripple dictionaries that this editorial mistake was introduced IMHO.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/pull/942#issuecomment-1544038362 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 May 2023 13:58:27 UTC