If two other platforms were able to implement this on a satisfactory way, I don't think this is an issue with the spec per se (although I'm sure a better spec would help a lot, I agree). And considering there is a native battery charge tooltip on every Android device, I'd say there is a way to subscribe to those in a safer way. With that, wouldn't the Android dev group/bug tracker be a better place for this feedback (to make it easier to use that safe route)?
2014-06-11 15:48 GMT-03:00 Marcel Kinard <cmarc...@gmail.com>: > And document why the current implementation is not recommended for app > developers to use, because people tend to use things that are available. > That’s the short term answer. > > The long term answer is to get help from jsoref and others to give > feedback to the W3C that their spec is unimplementable on the platform that > is the most popular in the market. I’d like to think that with an API > alignment, Cordova is the [early] implementor of W3C specs like this, and > we should be an invaluable proving ground and source of feedback for these > things. Whether or not the W3C can adjust in a timely manner is another > question (and not ours to answer), but we should be giving them technical > feedback on our implementation experience. > > On Jun 10, 2014, at 6:54 PM, Brian LeRoux <b...@brian.io> wrote: > > > shelve! > > -- *Frederico Galvão* Diretor de Tecnologia PontoGet Inovação Web ( +55(62) 8131-5720 * www.pontoget.com.br <http://www.pontoget.com/>
