Jump to content
|Topic||Stats||Last action by|
|Neowin Members Digital Gallery 2014||
|The Great Modern UI Debate Thread||
|windows 8.1 phone app permissions||
|Installing only to specific account||
|Security group claims they can forge fingerprints from a photo||
Posted 03 October 2012 - 07:17
Posted 03 October 2012 - 07:22
Posted 03 October 2012 - 15:04
What has Google done to the new font rendering mechanism? Fonts look a little bit lighter and condensed when compared to other GDI-rendering browsers (the ones not using HWA). Is it a new step to support DirectWrite rendering?
Posted 03 October 2012 - 16:16
Posted 03 October 2012 - 21:35
Yep, updated a few days ago and it looks ridiculous to my eyes.
Oh why are there not any decent font rendering extensions for Chrome
Posted 04 October 2012 - 18:32
Posted 06 October 2012 - 12:29
Posted 06 October 2012 - 17:48
as it's about updates in chrome thought this might be the best place to ask is there any way to get chrome to alert and ask me about updating just i like to have a landmark of sorts in time to help with trouble shooting.
Posted 08 October 2012 - 21:06
Stable Channel Update
Monday, October 8, 2012 | 10:00
Labels: Stable updates
The Stable channel has been updated to 22.0.1229.92 for Windows, Mac, and Linux. This update contains a number of stability fixes, including an issue with multiple profiles on Mac OS X 10.8.2. It also contains a fix for text display on the Mac, as well as the security updates listed below.
Security fixes and rewards:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.
[$1000]  High CVE-2012-2900: Crash in Skia text rendering. Credit to Atte Kettunen of OUSPG.
[$3133.7]  Critical CVE-2012-5108: Race condition in audio device handling. Credit to Atte Kettunen of OUSPG.
[$500]  Medium CVE-2012-5109: OOB read in ICU regex. Credit to Arthur Gerkis.
 Medium CVE-2012-5110: Out-of-bounds read in compositor. Credit to Google Chrome Security Team (Inferno).
 Low CVE-2012-5111: Plug-in crash monitoring was missing for Pepper plug-ins. Credit to Google Chrome Security Team (Chris Evans).
Posted 10 October 2012 - 07:24
Posted 10 October 2012 - 18:22
Posted 14 October 2012 - 09:48
Posted 17 October 2012 - 04:43
Posted 18 October 2012 - 03:36
Posted 18 October 2012 - 09:46
I'm wondering when they will fix the font rendering issue. Since Chrome v22 actually... either they are too thin or too bold depending of the websites.