Re: [w3ctag/design-reviews] API for display-capturing the current tab (#625)

Once the security measures `getViewportMedia` requires are sufficiently rolled out, applications will naturally migrate from `preferCurrentTab` to `getViewportMedia`, because the latter offers a superior UX; namely, the user is presented with a clearer choice, and cannot choose anything  **but** the current tab.

Chrome has UMA tracking calls to getDisplayMedia with/without `preferCurrentTab` (and the API invocation's result). getViewportMedia will be associated with similar UMA.

When we feel that adoption is sufficient, or that the challenges to it are no longer as significant, we can (a) communicate publicly that `preferCurrentTab` is about to be deprecate and (b) start printing deprecation warnings to the dev-console whenever it is used.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/625#issuecomment-919482899