241 replies to this topic 3 votes

[Mamoru-san]

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?

[+Mephistopheles]

Dev Channel Update

The Dev channel has been updated to 24.0.1284.2 for Windows, Mac, Linux, and Chrome Frame. This build contains following updates:

All

• Updated V8 - 3.13.7.1
  
• Updated WebKit - 537.13
  
• Fixed an issue where clearing browsing data would not complete when Pepper Flash was disabled (Issue: 144874)
  
• Fixed an issue where inline disposition isn’t displaying correctly. (Issue: 145622)
  
• Fixed a crash when clicking speech input. (Issue: 146689)
  
• Fixed file system URLs no longer work in platform apps. (Issue: 150861)
  
• Fixed a crash when opening YouTube in full screen mode. (Issue: 149821)
  
• Fixed a crash when loading explicit intent service. (Issue: 150834)

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome

Source: Google Chrome Releases blog

[RadishTM]

iMamoru, on 03 October 2012 - 07:17, said:

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?

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

[z0phi3l]

Fonts look fine on Chrome, and always have with the rare exception of a bug here and there

[Mamoru-san]

RadishTM, on 03 October 2012 - 15:04, said:

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

I wish they could do something like IE 9. Best font rendering ever!

[+Mephistopheles]

Beta Channel Update

The Beta channel has been updated to 23.0.1271.17 for Windows, Mac, Linux, and ChromeFrame. This build fixes some of the known stability issues. A complete log of what changed can be found in the svn revision log. If you find new issues, please let us know by filing a bug. Want to change to another Chrome release channel? Find out how.

Karen Grunberg
Google Chrome

Source: Google Chrome Releases blog

[+Azusa]

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.

[z0phi3l]

Azusa, on 06 October 2012 - 12:29, said:

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.

No it's supposed to self update without warning

[still1]

Quote

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] [138208] High CVE-2012-2900: Crash in Skia text rendering. Credit to Atte Kettunen of OUSPG.
[$3133.7] [147499] Critical CVE-2012-5108: Race condition in audio device handling. Credit to Atte Kettunen of OUSPG.
[$500] [148692] Medium CVE-2012-5109: OOB read in ICU regex. Credit to Arthur Gerkis.
[151449] Medium CVE-2012-5110: Out-of-bounds read in compositor. Credit to Google Chrome Security Team (Inferno).
[151895] Low CVE-2012-5111: Plug-in crash monitoring was missing for Pepper plug-ins. Credit to Google Chrome Security Team (Chris Evans).

[+Mephistopheles]

Dev Channel Update

The Dev channel has been updated to 24.0.1290.1 for Windows, Mac, Linux, and Chrome Frame. This build contains following updates:

All

• Fixed issue where clearing browse data never completes with PPAPI flash plugin disabled. [Issue: 144874]
  
• Fixed issue in disabling sync for default apps. [Issue: 152582]
  
• Fixed crashes 154167, 153902, 152622.

Known Issues

• Issue 154663: On Windows 8, if Chrome is set to use Windows 8 mode, it might launch in Windows 8 mode when trying to uninstall (and therefore fail to uninstall). Workaround: make another browser default (in Control Panel -> Default Programs) and then uninstall Chrome.

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome

Source: Google Chrome Releases blog

[still1]

60k??

Stable Channel Update

Wednesday, October 10, 2012 | 08:40
Labels: Stable updates

The Stable channel has been updated to 22.0.1229.94 for Windows, Mac, and Linux. This release contains fixes for the security issue listed below.

Security fixes and rewards:

Congratulations to Pinkie Pie, returning to the fray with another beautiful piece of work!

We’re delighted at the success of Pwnium 2, and anticipate additional hardening and future improvements to Chrome as a result of the competition.

• [$60,000][154983][154987] Critical CVE-2012-5112: SVG use-after-free and IPC arbitrary file write. Credit to Pinkie Pie.

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.

Full details about what's in this release are available in the SVN revision log. Found a bug? Report it! On a different channel, but want to join us on the Beta train? The Chromium wiki has you covered.

[+Jamushroom]

I'm wondering when they'll be updating the bookmark folder icons on the Windows version to a more modern looking icon. They've got "Windows 98" written all over them. Why not have it like the OSX version? Why not recolor those into having the same color as the OS's folder icons?

[+Mephistopheles]

Dev Channel Update

The Dev channel has been updated to 24.0.1297.0 for Windows, Mac, Linux, and Chrome Frame. This build contains following updates:

All

• Updated V8 - 3.14.4.1
  
• Updated WebKit - 537.16
  
• Fixed tab character in text field when pressed Tab in a <browser> tag. (Issue: 149859)

• Fixed omnibox suggestion: restore selection on WM_IME_ENDCOMPOSITION (Issue: 154379)
  
• Fixed text that goes out of the box under Related section after an app was installed. (Issue: 154797)
  
• Fixed Web Store icon (Issue: 149887)

Windows

• Updated styling for Web Intents windows
  
• Setting preference to launch in Metro on Windows 8 will no longer cause Chrome to launch in Metro mode upon uninstall.
  
• Fixed missing print preview on Asian sites. (Issue: 161704)

Mac

• Fixed a bug where Chrome would use an outdated version of Pepper Flash (Issue: 151716)
  
• [r161874] Fixed a bug where Chrome would fail to quit if at least two windows were open and a page had a beforeunload handler (Issue: 118424)
  
• Fixed browser hang when webcam used on facebook with OSX flapper. (Issue: 152757)

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome

Source: Google Chrome Releases blog

[msi75]

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.

[Marcel T]

msi75, on 18 October 2012 - 03:36, said:

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.

Have an example screenshot?