Exposing HW for Cloud Gaming use cases (HW encoder/decoder revisited)

w3c / webrtc-stats

WebRTC Statistics

https://w3c.github.io/webrtc-stats/

Other

128 stars 46 forks source link

Exposing HW for Cloud Gaming use cases (HW encoder/decoder revisited) #698

Closed henbos closed 1 year ago

henbos commented 1 year ago

We finally have a hardware exposure privacy mitigation, hurray!

@drkron mentioned there is one more use case where HW information may be needed, and that is Cloud Gaming. Unlike VC use cases, a Cloud Gaming app would not be using getUserMedia() (no audio/video capture in the context).

Cloud Gaming does do something that a passive fingerprint is not doing though: it runs in fullscreen.

Can we add "is fullscreen" to the list of conditions where HW exposure is allowed? @youennf @pes10k

henbos commented 1 year ago

I assume the app can't toggle fullscreen for a split millisecond without the user noticing... but if it could, the gating could say something like "fullscreen has been active for at least X seconds"...

henbos commented 1 year ago

@aboba might care about this too. For context, this PR just landed.

henbos commented 1 year ago

Proposal:

If document.fullscreenElement is not null, return true.

fippo commented 1 year ago

while that probably encompasses most gamestreaming use-cases you might want to add https://www.w3.org/TR/gamepad/#dfn-gamepad-user-gesture to be on the safe side