Re: [webkit-dev] Request for position: preferCurrentTab

> > Doesn't this property go against that conscious design decision? What is > your security analysis here? Both preferCurrentTab=true as well as preferCurrentTab=false result in a user-prompt that is spec-compliant. (The user agent is free to display the current tab as the most prominent option

Re: [webkit-dev] Request for position: preferCurrentTab

Hi Elad, At the time of getDisplayMedia design, people advocated against the ability for a web page to influence or restrict user choice, for security reasons. Doesn't this property go against that conscious design decision? What is your security analysis here? Also, getCurrentViewPort is trying

Re: [webkit-dev] Request for position: preferCurrentTab

We could rename to preferCurrentBrowserDisplaySurface, referencing a browser display-surface , but I find it to be a mouthful. But I'm open to suggestions. Name notwithstanding, what is Apple's official, quotable position? :-) On Thu,

Re: [webkit-dev] Request for position: preferCurrentTab

Hi Elad, Are there other existing uses of the term “tab” in other web exposed APIs? It feels a bit wrong to be wrong to be encoding that specific UI treatment into API. - Sam > On Jun 9, 2021, at 4:20 AM, Elad Alon via webkit-dev > wrote: > > This is a request for WebKit's position on

[webkit-dev] Request for position: preferCurrentTab

This is a request for WebKit's position on adding a dictionary member in MediaStreamConstraints called preferCurrentTab. If preferCurrentTab is set to true, the user agent will display the current tab as the most prominent option in the media-picker which getDisplayMedia invokes. Links: -