Recommended Posts

Stable Channel Update

Thursday, August 30, 2012 | 13:18

Labels: Stable updates

The Stable channel has been updated to 21.0.1180.89 for Linux, Mac, Windows and Chrome Frame

This build fixes the following issues:

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.

  • [$500] [121347] Medium CVE-2012-2865: Out-of-bounds read in line breaking. Credit to miaubiz.
  • [$1000] [134897] High CVE-2012-2866: Bad cast with run-ins. Credit to miaubiz.
  • [135485] Low CVE-2012-2867: Browser crash with SPDY.
  • [$500] [136881] Medium CVE-2012-2868: Race condition with workers and XHR. Credit to miaubiz.
  • [137778] High CVE-2012-2869: Avoid stale buffer in URL loading. Credit to Fermin Serna of the Google Security Team.
  • [138672] [140368] Low CVE-2012-2870: Lower severity memory management issues in XPath. Credit to Nicolas Gregoire.
  • [$1000] [138673] High CVE-2012-2871: Bad cast in XSL transforms. Credit to Nicolas Gregoire.
  • [$500] [142956] Medium CVE-2012-2872: XSS in SSL interstitial. Credit to Emmanuel Bronshtein.

Many of the above bugs were detected using AddressSanitizer.

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry

Karen Grunberg

Google Chrome

Dev Channel Update

The Dev channel has been updated to 23.0.1251.2 for Windows, Mac and ChromeFrame platforms.

All

  • Fixes several known top crashers (Issue: 144436)
  • Fixed tab strip menu not working (Issue: 144425)

Windows

  • IndexedDB.open no longer hangs on windows (Issue: 143680)

More details about additional changes are available in the svn log of all revisions.

You can find out about getting on the Dev channel here: http://dev.chromium....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Whats the difference between the Chrome Dev channel and Chromium?

Someone correct me if I'm wrong, but I believe Chromium builds are released nightly and have to be updated manually by downloading the binaries. The dev channel doesn't get updates quite as often as Chromium, but the browser updates itself.

Whats the difference between the Chrome Dev channel and Chromium?

Chromium is the open-source build, with several builds per day being produced.

Chrome dev channel builds come with the Google branding, auto-update etc. They come out once a week on average.

Dev Channel Update

The Dev channel has been updated to 23.0.1255.0 for Windows, Mac, Linux and ChromeFrame platforms

All

  • Fixed a crash which occurred when scavenging sessionStorages. (Issue: 145068)
  • Packaged Apps can now request access to local media folders.

Windows

  • Fixed a bug causing Chrome shortcuts to stop working on Windows 8 after an update. (Issue: 143338)
  • Can't scroll down by entering space after switching tab when IME is enabled (Issue: 80772)
  • Can't type Japanese/Korean into a text field in a Flash application on Window Vista/7 using MS Japanese IME and MS Korean IME (Issue: 75556)

Mac

  • Fix crash when playing video on MB retina (Issue: 141541)

More details about additional changes are available in the svn log of all revisions.

You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

So what version do you recommend for someone who likes to be on the cutting edge but still wants speed/functionality 99% of the time?

Since you mentioned bleeding (cutting) edge with speed and functionality then Dev branch is for you. But I still suggest you to use Beta over Dev channel because many times dev channel are totally blast off. Go ahead with Beta channel.

Any word on font rendering based on DirectWrite? I'm using Canary and it looks like some websites are rendered the same way Firefox renders when HA is on.

Not saw any changelog word with DirectWrite. Yes! I agree Chrome font rendering improved a lot.

You can check major changelog of Chrome font rendering library (it is actually multipurpose).

----------------------------------------------------------------------------

Share this page got icon as well:

szo9C.png

Chromium is the open source version of chrome and wont have auto update/book mark sync/cloud printing and all those Google features.

Chromium does have bookmark sync.

I didnt quite like the popup actually.. It should have been bookmark star and share symbol side by side in the omnibox

Same here. They could remove the share button for all I care. I just want easy access to the bookmark icon. My guess is they will revert in the next few builds.

Chrome new Share feature integration... in 23

Without Expansion in Omnibox:

w8BzH.png

With Expanding:

3aQgK.png

I'm on Dev and I don't have this and can't find this on flags as well. :/

Version 23.0.1255.0 dev-m

Edit: Nevermind, so it's the Action thing. It crashes on mine everytime I click it. Oh well, interesting concept. Extra click to bookmark but better than having a separate share button

I'm on Dev and I don't have this and can't find this on flags as well. :/

Version 23.0.1255.0 dev-m

Edit: Nevermind, so it's the Action thing. It crashes on mine everytime I click it. Oh well, interesting concept. Extra click to bookmark but better than having a separate share button

I am using Chromium snapshots.

This is my latest snapshots: 23.0.1261.0 (Build 155617)

Do Not Track header support is coming slowly.. One changeset of it:

Implement 'Do Not Track' header DNT support is currently under development. BUG=81844 https://codereview.c...um.org/10911283

------------------------

New closed hover state..

0F9uL.png

History option is also optimized for touch now.

Beta Channel Update

The Beta channel has been updated to 22.0.1229.56 for Windows, Mac, and Linux. A complete log of what changed can be found in the svn revision log. Instructions and download links for our different release channels are available on the Chromium wiki. If you find what you think is a new bug, please file it in our issue tracker.

Jason Kersey

Source: Google Chrome Releases blog

Hopefully they'll be concentrating on the download manager soon. I remember there being a flag at one point with a test UI. Can anyone confirm they're still working on that?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!