[webkit-dev] Proposal: Remove Battery Status API code
gyuyoung.kim at webkit.org
Sun Oct 30 18:26:09 PDT 2016
The battery status API has been used by EFL port so far. As far as I know
the feature was added to support
web application. But I'm not sure how many web applications have used it so
far.(Personally I guess it might be
used by few applications.) Besides unfortunately nobody maintains it now.
If there is concern to keep the feature
and other ports don't want to use it anymore, It looks I can't object to
On Mon, Oct 31, 2016 at 9:54 AM, Simon Fraser <simon.fraser at apple.com>
> I support the proposal to remove.
> > On Oct 30, 2016, at 5:14 PM, Brady Eidson <beidson at apple.com> wrote:
> > There's code in the tree to support the W3C Battery Status API.
> > A recent study showed the extent of the risk (discussion and link to
> study https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.
> tXRsbZBMid46hd9UXs&e= ) which led to Mozilla first making the API less
> precise (https://bugzilla.mozilla.org/show_bug.cgi?id=1124127) but then
> eventually removing it altogether (https://bugzilla.mozilla.org/
> > Apple has never enabled this on their ports, one reason being concern
> for abuse in fingerprinting/tracking.
> > The study seems to be a strong second opinion backing this concern.
> > Mozilla's actions demonstrate another vendor not seeing the API being
> useful enough to outweigh the user concern.
> > As one of the voices for Apple's ports I think the above episode further
> cements our concern in ever enabling the API.
> > As one of the voices for WebKit as a whole I think above episode
> suggests we should just remove the code from the tree altogether.
> > What to other Apple folks think? What do port maintainers who enable the
> API think?
> > Thanks,
> > ~Brady
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev