Do you mean dropping support only for Android, or dropping the plugin altogether? On some platforms it may still be relevant.
-----Original Message----- From: Jesse [mailto:[email protected]] Sent: Tuesday, March 24, 2015 10:31 AM To: [email protected] Subject: Re: [Android] Proposal: Deprecate/No-Op Battery Plugin Can we drop our support for the battery plugin entirely? Let the community take over if they want it? I would rank it very low in use among our supported plugins, but it does probably still need to exist. > On Mar 24, 2015, at 9:46 AM, Joe Bowser <[email protected]> wrote: > > Hey > > So, right now our current Battery Plugin on Android is actually > considered harmful to devices and shouldn't be used. It seems that > the Chrome team has implemented the Battery Spec in Chromium 38. This > can be tested with this simple JSBin here: > > http://jsbin.com/battery-status-test > > The problem is that Android WebView on Lollipop that's installable > from the Play Store is at 37, and of course I don't even have to > mention earlier Android versions that we support, some of which don't even > support Chromium. > > However, the latest Crosswalk does support the Battery Spec, so we > have two > options: > 1. Implement a plugin for the non-Crosswalk use case, knowing that > it'll be obsolete for Future Android. We always intend to do this, > but this never, ever happens. > 2. We drop support the Battery Plugin for Android since nothing in > this case is better than something that's actively draining your battery. > > What do people think of this? > > Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
