- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jul 2020 01:54:21 +0000
- To: public-device-apis-log@w3.org
It seems pretty unlikely those we would count those as implementations for the purpose of progressing the specification along the recommendation track, right? At least, without subverting the W3C process. [3] clearly shows that this doesn't have "wide support" in the same way we would consider other platform features (implemented in Gecko and WebKit) - only really single engine support, so it's pretty unlikey to reach REC status. > Notably, the API is used in ~11% of page loads in Chrome per Chrome usage metrics. This should ring alarm bells. Do we know what possible reason a web page have to accessing this API? such high usage points to it being used by one or more trackers. > DAS WG is a global community that encourages implementations also by browsers not known to the Western world. That's great! And all browsers engines are open sources so people from all over the world contribute to them, but there only 3 of them - so we can't really count chromium wrappers are independent implementations. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/98#issuecomment-655848891 using your GitHub account
Received on Thursday, 9 July 2020 01:54:23 UTC