Javascript setTimeout timers are not getting expired when app in background
Reported by
ambercoo...@gmail.com,
Oct 20 2016
|
|||||
Issue descriptionSteps to reproduce the problem: 1. Android application running in background (white listed) 2. Call setTimeout api with a callback and timer of 60000 (60 sec) 3. Callback is not invoked after 60000 ms. (No other tasks are running on main thread) What is the expected behavior? Callback should be invoked after 60 sec What went wrong? callbacks are not getting invoked after given timers Did this work before? Yes on webview version 52 Chrome version: 53.0.2785.143 Channel: stable OS Version: Android 6.0 Flash Version: Shockwave Flash 23.0 r0
,
Oct 20 2016
,
Oct 21 2016
Yes, issue is with WebView within Android app
,
Oct 21 2016
I can not reproduce it on Nexus 6P with Android build NRD90 with the build 56.0.2891.0 (AndroidWebView). Please test with the latest version and reopen if the problem shows up.
,
Oct 24 2016
Can you provide the actual app you're using, ideally a minimised example with source code? Without that it's not really possible to reproduce this. Also, does this still reproduce on M54 (the current stable version) or M55 (the current beta)?
,
Oct 27 2016
Thanks , we will test with M54 and M55 beta and update you.
,
Nov 3 2016
We are not observing this issue on M54 and M55 beta release but we will monitor it for some more days. Thanks
,
Sep 13 2017
Effort from the triage Team: There is no active investigation / updates since the last couple months,closing the issue. Feel free to reopen if needed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by chrishtr@chromium.org
, Oct 20 2016Components: -Blink Mobile>WebView
Labels: -Pri-2 M-53 Pri-1