- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 May 2024 22:56:54 +0000
- To: public-device-apis-log@w3.org
I understand, but can you help me understand what the value or utility of this API is (specifically if it’s being updated) Let’s imagine WebKit had never seen this, why would we implement it and expose it to the Web Platform? I looked at #25 and most of those cases (specifically the media ones) are covered by more sophisticated solutions, like Managed Media Source. So I’m still unsure what value or use cases this API brings (and by implication why the W3C would then Recommend WebKit and other engines implement it). As you can hopefully understand, WebKit takes things ending up on the Rec Track seriously, so we want to understand why this being Recommended to us to implement? -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/battery/issues/64#issuecomment-2128164220 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 May 2024 22:56:56 UTC