Fixed
Status Update
Comments
ja...@jamesscholes.com <ja...@jamesscholes.com> #2
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 <pe...@chromium.org> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
va...@chromium.org <va...@chromium.org> #4
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
si...@sinabahram.com <si...@sinabahram.com> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
[Deleted User] <[Deleted User]> #6
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
al...@chromium.org <al...@chromium.org> #7
same
al...@chromium.org <al...@chromium.org> #8
SAME ! - Google can't do sth working in 100 percent?
al...@chromium.org <al...@chromium.org> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ja...@igalia.com <ja...@igalia.com> #10
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
ja...@igalia.com <ja...@igalia.com> #11
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
bu...@chops-service-accounts.iam.gserviceaccount.com <bu...@chops-service-accounts.iam.gserviceaccount.com> #12
Same issue here.
si...@sinabahram.com <si...@sinabahram.com> #13
Same issue here. How can i fix this bug?
ja...@igalia.com <ja...@igalia.com> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
ja...@igalia.com <ja...@igalia.com> #15
Thanks for the update @sbarta. It is good that you are keeping us informed. This is a very critical and blocking bug for anyone developing with maps.
is...@google.com <is...@google.com> #16
FYI also getting same with PlusClient sign in, so this is not just a maps issue:
ConnectionResult.SERVICE_VERSION_UPDATE_REQUIRED
07-30 12:35:50.059: W/GooglePlayServicesUtil(16054): Google Play services out of date. Requires 3159100 but found 1013
ConnectionResult.SERVICE_VERSION_UPDATE_REQUIRED
07-30 12:35:50.059: W/GooglePlayServicesUtil(16054): Google Play services out of date. Requires 3159100 but found 1013
Description
Steps to reproduce the problem:
Open the attached example and read with a screen reader or inspect with any accessibility tool.
3.
What is the expected behavior?
The expected behavior is demonstrated under the "working" heading in the example file. The outermost figure should respect it's only direct descendant of figcaption, instead it associates the figcaption of the first nested figure as the parent figure's figcaption.
What went wrong?
The figcaption associated with the outermost figure in the broken case is incorrect.
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 80.0.3987.132 Channel: stable
OS Version: 10.0
Flash Version: