- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Sep 2023 13:18:18 +0000
- To: public-webrtc-logs@w3.org
> If what we are after is allowing web pages to know that a device was inserted, exposing this information without relying on web page enumerateDevices()-based computation will probably give more interoperable results. I'm OK with adding a `reason` or similar field to the event as long as we keep it flexible enough not to make implementations not spec compliant for firing the event in a case that doesn't cleanly match one of the possible values in the field. A possible way to do it is by adding a `other` value as cause. My view is that: 1. Applications are more interested in knowing the latest state than the cause for a change in the state. 2. Having a cause can help in some cases (it would be good to document those). 3. As time passes, an implementation might find a new reason to fire the event, and it would be good if it could fire the event without breaking compliance with the spec. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/972#issuecomment-1740885290 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 29 September 2023 13:18:20 UTC