Revisit: Persisting permissions

[eladalon1983]

Wrt:

Like getDisplayMedia(), the "granted" permission cannot be persisted.

getViewportMedia has strict security requirements that could hamper adoption (cross-origin isolation and the document policy). We should do all we can to make the effort worthwhile to developers. The possibility of persisting permissions could tip the scales here. Let's discuss whether this is possible.

(nit: "permission cannot be persisted" - Do you want to change "cannot" to "MUST NOT"?)

[jan-ivar]

I think this tends to be a user agent choice, so we should perhaps consider this. I would object to a "MUST persist" however.

[eladalon1983]

@youennf raised an interesting question about persisting permissions when the last call approved {video}, {audio} or {video, audio}.

[youennf]

getViewportMedia has strict security requirements that could hamper adoption (cross-origin isolation and the document

Glad mentioned this issue during element capture breakout session at TPAC.
Some ideas were brought to reduce adoption barrier for element capture, which might be useful as well for getViewPortMedia.
For instance anonymous iframes..
It seems worth looking at this area.