- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jul 2020 01:38:06 +0000
- To: public-device-apis-log@w3.org
> fingerprintjs/fingerprintjs2#55 That issue was closed in 2016, so might warrant new investigation. Again, the fact that 11% of sites are reporting using this API rings alarm bells. > Some (but not all) MiniApp implementations support getting battery information. Like in this case, that doesn't equate to legitimate uses of the API (i.e., non-tracking ones, inline with the use cases). Exposing the API doesn't really mean much. @pes10k, as someone who works with the Chromium community, could you check if anyone has sent a patch to plug the Permissions Policy hole as well as the `SecureContext` hole? The spec claiming to be private to be private by just adding Permission Policy and `SecureContext` but then not having engines follow through on that is really frustrating. Can we change this group's working mode so that things don't land in specs before they implemented or have real implementation commitment? Otherwise, we are just pretending to make the web better and again misusing the W3C process. All specs in this group should be using: https://github.com/w3c/web-share/blob/master/.github/PULL_REQUEST_TEMPLATE.md to avoid us getting into this situation going forward. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/98#issuecomment-661540757 using your GitHub account
Received on Tuesday, 21 July 2020 01:38:08 UTC