In Blink, some features are internally tied to page visibility. These APIs are disabled when the page is not visible: Geolocation, Vibration, Device Motion. The goal is to save battery and CPU. In the case of the Vibration API, this behavior is explicitly specified in the spec. We should make sure to avoid affecting these APIs unintentionally. E.g. if an iframe is scrolled off screen these should probably not stop working. Or maybe they should? Regards, Michael On Mon, Jan 27, 2014 at 6:19 AM, Arvind Jain <arvind@google.com> wrote: > Agreed. I'll check with Chrome folks tomorrow. > > Arvind > > > On Sun, Jan 26, 2014 at 6:02 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > >> On 1/25/14 8:24 AM, Arvind Jain wrote: >> >>> Yes it is unfortunate that we are suggesting a non-compatible change. >>> Earlier in this thread, we discussed this - I'm pasting that exchange >>> below. Please let us know what you think we should do. >>> >> >> If we think we want to make this change, then what we _should_ do is get >> UAs to change behavior ASAP, and pray that there is no one depending on the >> old behavior yet. The longer the old behavior sticks around, the harder it >> becomes to change. >> >> Any UAs volunteering to go first? >> >> -Boris >> > >
Received on Monday, 27 January 2014 14:33:18 UTC