Re: [mediacapture-screen-share] Add ability to crop a MediaStream obtained through the share-this-tab API (#158)

> I would be open to an option if the default is "self".

Or better yet - don't allow a default. Force the application to be explicit. Wdyt?
(Not a critical point for me, but otherwise we might get into a situation where initially, some browsers only supports the less technically-challenging non-default version, and nobody benefits from that.)

> So I see little value in a user agent communicating that the grant is of a section smaller than the page

That is precisely my point. I think user agents are very likely to provide a preview, as this gives a clear indication of what the user approves - much better than text that never gets read. The preview will **always** consist of the entire tab - independently cropping, because the cropped region can change unexpectedly (due to layout changes). Supporting (also?) an un-cropped variant of this API is therefore the elegant thing to do.

> it becomes surprising to users what is actually being captured

There is no room for surprise or confusion. The end-user consents to capturing the entire tab, always. Anything else is inscrutable to them. As far as the end-user knows, it's the application which crops the frames; the end-user neither knows nor cares that the UA serves as the scissors.

> I don't think we should add "node". .. The utility here seems low

I see cropping to an arbitrary iframe (not node) as a use-case of utmost importance. When capturing the current tab, it is very likely that you're capturing from a VC-iframe, but want to stream the content-iframe, where "content" is a doc/slide/game/video/you-name-it. Some have argued for making tracks/stream transferrable, but I don't see that as a good alternative, as I have explained.

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-863338821 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 17 June 2021 15:30:39 UTC