- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Sep 2016 08:53:28 +0000
- To: public-media-capture-logs@w3.org
> If we then add track C with constraints that allow only for a setting of 1 or 3, it should be rejected To be specific, here you picked the same outcome I would. The alternative would be to allow track C and fire OverconstrainedError on track B instead, which also produces two working tracks, but I don't like it, because it seems less predictable, and undesirable for tabs to affect others in this way. That's why I prefer first-come-first-serve here. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/394#issuecomment-248551003 using your GitHub account
Received on Wednesday, 21 September 2016 08:53:39 UTC