After #712 has been merged, it is no longer possible to get the decoder fallback information in case of cloud gaming services which do not require hardware access permission in general use cases.
And the decoder fallback information is highly important to assess the session information whether the session has been fully accelerated by the hardware decoder or not. So I would like to propose adding decoderFallback in RTCInboundRtpStreamStats to get the information without hurting the security concern.
If the first proposal is not acceptable, as an alternative, I would also like to propose to remove fingerprint restriction on powerEfficientDecoder in RTCInboundRtpStreamStats.
My justification behind the second approach is that the powerEfficientDecoder can be modifiable when the decoder is getting fallback to the software decoder, so it is not a static variable to represent a user agent.
After #712 has been merged, it is no longer possible to get the decoder fallback information in case of cloud gaming services which do not require hardware access permission in general use cases.
And the decoder fallback information is highly important to assess the session information whether the session has been fully accelerated by the hardware decoder or not. So I would like to propose adding decoderFallback in RTCInboundRtpStreamStats to get the information without hurting the security concern.
If the first proposal is not acceptable, as an alternative, I would also like to propose to remove fingerprint restriction on powerEfficientDecoder in RTCInboundRtpStreamStats.
My justification behind the second approach is that the powerEfficientDecoder can be modifiable when the decoder is getting fallback to the software decoder, so it is not a static variable to represent a user agent.