Funny that would be causing you issues. The motivation for making it was to make the bridge work on the KitKat chromium-based WebView. Without it, no event would fire when an even number of messages were sent from native->js (since the online state would be the same as when it started, Chromium is smart enough to not send an event).
That was on my task list to share with the team, and to write a blog post about apps updating to Cordova 3.1 / 2.9.1 in order to pick up the fix and not have this race condition on KitKat. On Thu, Nov 7, 2013 at 4:05 PM, Naik, Archana <[email protected]> wrote: > Hi, Andrew > > I am working on amazon-fireos port for cordova. Amaozn-fireos port is > based on cordova-android. > We are currently testing our final bits before we go out for public > review. When testing 3.1.x, branch we noticed most tests are failing in > mobile spec. > After digging deep, we realized that your commit which tweaked few things > for online/offline events caused this failures on our AmazonWebView which > has chromium based web app runtime. > Here is the commit : > https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=166b35bc6c5977cf547f4093690d554b57cb855a > > Could you please explain what you are trying to do here? It just could > very well be the bug in our code but I want to understand your changes > so I can better debug in our chromium port. > > Thank you, > Archana >
