We introduce a dictionary member to MediaStreamConstraints called preferCurrentTab. It's a boolean defaulting to false. When getDisplayMedia() is called with preferCurrentTab=true, the browser should offer the current tab as the most prominent capture source.
This change does not merit any modifications to DevTools.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDPdovQG_CCBNP1dNNfM-amYt_Cdk88iBbrsVVVcnvv2SQ%40mail.gmail.com.
This is a non-trivial tradeoff, where another vendor (Mozilla) thinks this is a bad idea, while there are web developers expressing strong interest in this.For me, the balance tilts in the direction of "ship it" for a few reasons.First, the feature is really a UI hin with minimal web-exposed surface, a new dictionary member. The mere support of a dictionary member can be detected, but it takes extra work and isn't something I've ever seen content depend on. In other words, future site compat issues for other browsers that don't support this are very unlikely.Second, we have multiple web developers working on different web properties saying that this would be valuable to them. It's much stronger web developer feedback than we usually have. (It was requested, so it's not accidental, but still.) I think this will also be used on some Google web property, but it has wider usefulness.Mozilla's position, then:+Anne van Kesteren isn't sure about exposing the "tab" terminology. I agree that's novel in an unfortunate way, but the term (top-level) browsing-context isn't exposed to web developers now either. I think we could go along with any name here, given concrete suggestions.+Jan-Ivar Bruaroey points to the requirements of Screen Capture: "The user agent MUST let the end-user choose which display surface to share out of all available choices every time, and MUST NOT use constraints to limit that choice. ... This prevents an application from influencing the selection of sources." The point of preferCurrentTab is indeed to influence the selection, but it doesn't use constraints to limit the selection. I don't think this is quite a willful violation, but still worth calling out, so I've filed this issue. (Note that a willful violation could be OK, I'm not saying that we should take the requirement of Screen Capture as gospel.)The UI changes for this will also or perhaps have already gone through security review, I'm not making any evaluation of that.LGTM1On Thu, Jul 22, 2021 at 5:51 PM 'Elad Alon' via blink-dev <blin...@chromium.org> wrote:
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
LGTM2 for similar reasons to those Philip outlined.
On Friday, July 23, 2021 at 2:58:45 PM UTC+2 Philip Jägenstedt wrote:
This is a non-trivial tradeoff, where another vendor (Mozilla) thinks this is a bad idea, while there are web developers expressing strong interest in this.For me, the balance tilts in the direction of "ship it" for a few reasons.First, the feature is really a UI hin with minimal web-exposed surface, a new dictionary member. The mere support of a dictionary member can be detected, but it takes extra work and isn't something I've ever seen content depend on. In other words, future site compat issues for other browsers that don't support this are very unlikely.Second, we have multiple web developers working on different web properties saying that this would be valuable to them. It's much stronger web developer feedback than we usually have. (It was requested, so it's not accidental, but still.) I think this will also be used on some Google web property, but it has wider usefulness.Mozilla's position, then:+Anne van Kesteren isn't sure about exposing the "tab" terminology. I agree that's novel in an unfortunate way, but the term (top-level) browsing-context isn't exposed to web developers now either. I think we could go along with any name here, given concrete suggestions.+Jan-Ivar Bruaroey points to the requirements of Screen Capture: "The user agent MUST let the end-user choose which display surface to share out of all available choices every time, and MUST NOT use constraints to limit that choice. ... This prevents an application from influencing the selection of sources." The point of preferCurrentTab is indeed to influence the selection, but it doesn't use constraints to limit the selection. I don't think this is quite a willful violation, but still worth calling out, so I've filed this issue. (Note that a willful violation could be OK, I'm not saying that we should take the requirement of Screen Capture as gospel.)The UI changes for this will also or perhaps have already gone through security review, I'm not making any evaluation of that.LGTM1On Thu, Jul 22, 2021 at 5:51 PM 'Elad Alon' via blink-dev <blin...@chromium.org> wrote:
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMO6jDPdovQG_CCBNP1dNNfM-amYt_Cdk88iBbrsVVVcnvv2SQ%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e307f81a-b6c5-4fa4-a620-1c220749a9e9n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9452c80f-b717-4885-8b55-470a54717823n%40chromium.org.