Obsolete
Status Update
No update yet.
Comments
jh...@chromium.org
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
pe...@chromium.org
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
de...@gmail.com
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
[Deleted User] <[Deleted User]>
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
ya...@chromium.org
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
de...@gmail.com
same
ks...@google.com
SAME ! - Google can't do sth working in 100 percent?
kk...@chromium.org
same issue - Google Play services out of date. Requires 3159100 but found 3158130
kr...@chromium.org
Having the same issure:
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
kr...@chromium.org
API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
is...@google.com
Same issue here. How can i fix this bug?
Description
Chrome Version : 80.0.3987.149 (Official Build) (64-bit) (cohort: Stable)https://codepen.io/dested/pen/OJyLVRj
URLs (if applicable) :
What steps will reproduce the problem?
(0) Be in the mobile version of chrome, or the mobile simulator enabled from the dev tools in chrome desktop.
(1) Add a setInterval(()=>{},somethingSmallLike16)
(2) Add a div with the style touch-action:none;
(3) Tap on the div, or tap and hold for half a second or so
(4) The setInterval will not fire during a good portion of that time (even though things like requestAnimationFrame still fires faithfully). On windows I have see it hang for up to 120ms
What is the expected result?
The setInterval continues to fire on the scheduled interval
What happens instead?
It throttles the timeout for an undisclosed amount of time
Please provide any additional information below. Attach a screenshot if
possible.
Make sure you view the website above in either mobile chrome (tested on android, pixel 4, latest chrome) or enable the mobile simulator in the chrome dev tools (tested on windows 10, latest chrome). It should be trivially reproducable.