Yeah, I think we shouldn't break users. That said, I do think PauseOnBackground should be a new feature. I don't know if it'll land in 6.0 though, since I want to get the vote out this week.
On Tue, Oct 4, 2016 at 10:40 AM, Shazron <shaz...@gmail.com> wrote: > We could like you said make a breaking change, but allow a preference to be > set. > > We either make the preference backwards compatible (ie KeepRunning = true) > so existing apps still work the same on Cordova-Android 6, or break > backwards compatibility with KeepRunning=false as default. > > I would prefer to be backwards compatible, and not break users -- I think > if they encounter a rejection they can just turn on this preference and > re-submit. > > > > On Mon, Oct 3, 2016 at 4:23 PM, Joe Bowser <bows...@gmail.com> wrote: > > > Hey > > > > So, this bug came in and it's an important one: > > https://issues.apache.org/jira/browse/CB-11935 > > > > I've already accepted the fix for KeepRunning = false, but apps that > start > > in the background that have their JS running, and other apps probably > need > > to have their status managed. I want to run onPause and onResume on the > > webview every time the app pauses and resumes in Cordova, but I'm > wondering > > if that screws people up. I know that we're at the eve of a major > change, > > so I can just break stuff, but it'd be good to get feedback before doing > > it. > > > > What do people think? This is a pretty important change. > > > > Joe > > >
