- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Mar 2022 13:33:21 +0000
- To: public-webrtc-logs@w3.org
> We can't because of the design principle I [mentioned above](https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1064571776), so we need to decide on the default first. Clarification: I don't mind if it's excludeCurrentTab or includeCurrentTab. Given that you can cite a an established principle for making it includeCurrentTab, I am 100% OK with that, and everything else in my comment assumes this change. To avoid distraction, I try to use "default-include-current-tab", as it would otherwise be confusing if I mean "default-false" to include/exclude. Could you please re-read [my comment](https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1064947585) in light of this clarification? > Thanks, but I don't accept this as a use case, because it seems trivial (better even) to open the Loom page you want to record in a separate tab (which lets you demo any page, not just ones with recording controls embedded in them). It's also trivial to install a native app when Web applications can't do what the end-user wants, and end up contorting themselves in Web-y ways that the end-user assumes is due to lack of polish. > allow apps to express that A) they want self-capture, or B) they don't want self-capture. Whether they get it or not we already decided was irrelevant (a hint). I prefer A, because most sites are in B. I think this refers to the solved question of include vs. exclude. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/209#issuecomment-1066791742 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 March 2022 13:33:23 UTC