Fixed
Status Update
Comments
re...@igalia.com <re...@igalia.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
em...@chromium.org <em...@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"
re...@igalia.com <re...@igalia.com> #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
re...@igalia.com <re...@igalia.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
re...@igalia.com <re...@igalia.com> #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
re...@igalia.com <re...@igalia.com> #8
SAME ! - Google can't do sth working in 100 percent?
re...@igalia.com <re...@igalia.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
fu...@chromium.org <fu...@chromium.org> #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
fu...@google.com <fu...@google.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.
is...@google.com <is...@google.com> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
Description
Currently third_party/blink/renderer/core/html/resources/html.css has the following code:
:focus {
outline: auto 1px -webkit-focus-ring-color
}
This causes that when you click an element like:
<div tabindex="0">foo</div>
The element gets a focus ring (an outline).
That's precisely what :focus-visible is trying to avoid, so now that it has shipped we should change the UA stylesheet to use :focus-visible directly.
Also this will align Chromium with the spec text (
"User agents should also use :focus-visible to specify the default focus style, so that authors using :focus-visible will not also need to disable the default :focus style."
See
BTW, in Firefox you don't get a focus ring when you click an element like that.