Are you serious..Wtf are they thinking? DirectWrite looks HORRIBLE and strains my eyes. Same reason I turned off ClearType in Vista and had to switch system fonts in 7 since it was forced all the time.Used to be a simple option in flags, then we were forced to disable it there and use a command line switch.. and now it's going away entirely. This is worse than smooth scrolling being forced on us.Google have lost their minds as much as Mozilla. And here Chrome has been my fallback browser because of Firefox's changes.
Hi, what is the difference between this announcement and the one from July 26th? When July 26th release came out I never got the update to Chrome 52 on my devices however today, I did.http://googlechromereleases.blogspot.ca/2016/07/stable-channel-update-for-chrome-os_26.html
What Mac Pham said.
Are there any people experiencing issues with their tests failing since this update? Across a number of different projects we are having failures. Could be a red herring. Thoughts appreciated.
Anyone else having Bluetooth audio problems after this update? The mic on our Jabra SPEAK 510 is suddenly overdriven and garbled. Completely unusable. It still works fine on an iPhone and a MacBook Pro.
This update broke our test automation using Selenium, running on Jenkins as a Windows service. The workaround is explained at https://groups.google.com/forum/?hl=en#!topic/selenium-users/gfvfH-YEC48
where is DirectWrite option (chrome://flags)? 52.0.2743.116 version of chrome - becomes horrible fonts look
Fonts look abysmal.. like someone has barfed on my screen... WTF ?
Post a Comment