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

> But no, Brave has no intention to do any work at all implementing anything relating to the battery API. We don't support it.

Really, then what's this? 

![Screen Shot 2020-07-31 at 12 08 32 pm](https://user-images.githubusercontent.com/870154/88992362-8f9efa00-d326-11ea-9715-ea030c574e43.png)

Please understand why I'm getting really pissed off here: Brave is part of the Chromium project and you ship the API (I guess you didn't know that, surprise! 🎉 ), but you seem unwilling to go an actually fix stuff in the Chromium project you depend on. 
 
Anyway, seems like the only solution here is remove `SecureContext` and Permissions Policy integration from the spec until someone has the actual guts step up and actually implement/ship secure contexts and Permission Policy.  

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 31 July 2020 02:12:50 UTC