W3C home > Mailing lists > Public > public-device-apis-log@w3.org > August 2020

Re: [dap-charter] DASWG: Drop Battery API for privacy and lack of implementer support (#98)

From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 Aug 2020 03:47:34 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-667787922-1596426453-sysbot+gh@w3.org>
Oh, that's great to see @reillyeon. Thank you! Looks like Blink folks are coming to the same conclusions. If the mitigations get shipped, I'm still betting on usage going down to 0.00n% usage (and this becoming non-harmful). At the same time, I'm hopeful we can see some legit breakage, so to allow us to deal with those legitimate cases better (e.g., if YouTube is actually using it for some codec selection, then that's probably better done in the `<video>` element or whatever). 

At the same time, it seems Dev Tools is in a way better position to provide accurate battery consumption information on a per tab basis (see "about:performance" in Firefox), which provides a real time view of energy impact of a tab. 

<img width="1277" alt="Screen Shot 2020-08-03 at 1 47 05 pm" src="https://user-images.githubusercontent.com/870154/89143992-d4799980-d58f-11ea-9719-9c738b7047eb.png">

-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/98#issuecomment-667787922 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 August 2020 03:47:36 UTC

This archive was generated by hypermail 2.4.0 : Monday, 3 August 2020 03:47:37 UTC