- From: pes10k via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Mar 2023 00:27:33 +0000
- To: public-webrtc-logs@w3.org
> @pes10k Could you please review my feedback on the decoderFallback approach from the FP protection perspective once again? Ah i see, can you say more about the kinds of cases that would cause `decoderFallback` to be true? I thought `decoderFallback` just meant "software renderer", which could be true for all sorts of persistant reasons (the device doesn't have relevant hardware, or the OS has been upgraded/ changed and so the hardware isn't supported, etc). Could you give some other examples of when `decoderFallback` would be true, and which would be temporary vs semi-persistant? > Also could you share a little more detail about how to define the "high-touch event"? Sorry, I didn't mean to mislead you, this isn't a well defined term. I just mean "some high level of interaction or user intent". The most common examples are dialogs and permission prompts, but those aren't the only ones -- GitHub Notification of comment by pes10k Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/730#issuecomment-1452764494 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 March 2023 00:27:35 UTC