Re: [mediacapture-main] "user-chooses": Does required constraints make any sense now? (#669)

@henbos I think you have raised a lot of good questions.  Thank you. 

Overall, we are really talking about a very different model from the current Media Capture approach, much more like Screen Capture.  Just as Screen Capture forced us to re-think the role of constraints, it seems to me that an "in-chrome" approach to Media Capture will require some new thinking. 

Given that we are really talking about a new model, I am wondering whether the right way to handle this might be to create a new "Media Capture and Streams Version 2" work item, rather than trying to make all these changes to the existing Media Capture and Streams document before bringing it to PR.

This doesn't imply a new API,  just that we use separate documents for the old approach and the new one, so that we can clearly document each one.  Otherwise, I am concerned that we could confuse the reader, who will not be able to distinguish "old" from "new" approaches.



-- 
GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/669#issuecomment-603668177 using your GitHub account

Received on Wednesday, 25 March 2020 06:39:10 UTC