WAI
Status Update
Comments
pa...@google.com <pa...@google.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
vl...@gmail.com <vl...@gmail.com> #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"
pe...@google.com <pe...@google.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
vl...@gmail.com <vl...@gmail.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
st...@google.com <st...@google.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
vl...@gmail.com <vl...@gmail.com> #8
SAME ! - Google can't do sth working in 100 percent?
pk...@google.com <pk...@google.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
vl...@gmail.com <vl...@gmail.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
ke...@chromium.org <ke...@chromium.org> #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
vl...@gmail.com <vl...@gmail.com> #12
Same issue here.
vl...@gmail.com <vl...@gmail.com> #13
Same issue here. How can i fix this bug?
Description
Steps to reproduce the problem
Problem Description
Text rendering should happen like this: compute the final font size, and render the font at that font size. (Fonts with so-called bitmap strikes then render without blur.) But what might be happening in the favicon (tab bar) instead is this: compute some preliminary font size, render the text, then resize the rendered image. As a result, the favicon looks blurred for all values of
font-size
I tried. On the other hand, the same image on the page looks sharp for many of thewidth
values. In Firefox, the favicon (tab bar) looks good.Summary
Blurred fonts with bitmap strikes in SVG favicons
Additional Data
Category: UI
Chrome Channel: Not sure
Regression: N/A