- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 May 2016 21:00:04 +0000
- To: public-media-capture-logs@w3.org
There's no observable difference in what the name/ID is; as I said that's up to you. I think consistency with fullscreen makes sense given how similar the features are, but we could name it the "allowusermedia flag" if you want; no big deal. As for browsing context vs. document, I believe in this case there is probably no difference. For fullscreen it has to be per-document, because you can do things like ```js var doc = document.implementation.createHTMLDocument(); doc.body.requestFullscreen(); ``` and here `doc` does not have a browsing context. But for getUserMedia this does not apply. I can restructure the HTML patch to be per-browsing context if that is preferred, but I thought staying consistent with fullscreen's structure (of making it per document and propagating it upon document creation) would be easier for implementers to reason about. Let me know what you think. /cc @annevk for discussion of fullscreen's fullscreen enabled flag. -- GitHub Notification of comment by domenic Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/353#issuecomment-217668569 using your GitHub account
Received on Saturday, 7 May 2016 21:00:05 UTC