- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Jan 2017 08:03:40 +0000
- To: public-media-capture-logs@w3.org
I just validated my hypothesis: if we drop the other `<dfn>`s for `videoKind` we'll get the following warnings: ``` No <dfn> for videoKind in MediaTrackCapabilities. No <dfn> for videoKind in MediaTrackConstraintSet. No <dfn> for videoKind in MediaTrackSettings. ``` The same applies to the following members too defined in multiple dictionaries (the CI check halts on the first error so these go unnoticed): ``` depthNear depthFar focalLengthX focalLengthY ``` Given "`No <dfn> for XXXXX`" warnings is better than the current errors, I suggest we keep `<dfn>`s for the above dictionary members only in `MediaTrackSupportedConstraints` and remove `<dfn>`s from any other dictionaries as we figure out how to fix this properly. That said, the warnings would not block this PR from being merged. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/mediacapture-depth/pull/149#issuecomment-274422465 using your GitHub account
Received on Monday, 23 January 2017 08:04:16 UTC