Recommended Posts

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.

They're problem trying to get HWA font rendering to work in Chrome. A shame it looks messy, though.

There is an extension that allows you to change de CSS fonts in a website. Try downloading something like "font changer" on Chrome Webstore and use Segoe UI or Lucida Grande to render websites. Looks A LOT BETTER.

After using Firefox for roughly 6 or 7 years then using Chrome for about 2 years, I think I'm going back to firefox (64-bit) today. There are just so many little instances of things that never get fixed -- for example: still no option to automatically close the downloads bar after a DL completes, or the fact that in the latest Chromium builds, a Chromium desktop shortcut is created every time you launch the browser. I've opened up bug reports at http://code.google.com/p/chromium/issues but they've gone nowhere

Dev Channel Update

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

All

  • Updated V8 - 3.14.5.0
  • Bookmarks are now searched by their title while typing into the omnibox with matching bookmarks being shown in the autocomplete suggestions pop-down list. Matching is done by prefix. Example: if there is a bookmark with a title of ?Doglettes & Catlettes? typing any of the following into the omnibox will likely present the bookmark as a suggestion:: ?dog?, ?cat?, ?cat dog?, ?dog cat?, ?dogle?, etc. Typing ?ogle? or ?lettes? will not match.
  • Fixed issues 155871, 154173, 155133.

Windows

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

Dev Channel Update

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

All

  • Updated WebKit - 537.17
  • Fixed bugs related to bookmark sync and stability issues like 157365, 155871

Linux

  • Fixed GPU process crash on startup if stderr cannot be closed (Issue: 152530)

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

Dev Channel Update

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

  • Fixed getUserMedia video-only requests which should not fail if no audio input device is present. (Issue: 144421)
  • Fixed infobar prompt for Windows 8. (Issue: 158419)
  • Fixed drag and drop to install extensions. (Issue: 158499)
  • Fixed NaCl games for Windows 8. (Issue: 153368)
  • Fixed few stability issues 134175, 158745, 155653, 158377, 158660, 158703, 158176.

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

Stable and Beta Channel Update

The Chrome team is excited to announce the release of Chrome 23 to the Stable Channel. 23.0.1271.64 for Windows, Mac, Linux, and Chrome Frame. Chrome 23 contains a number of new features including GPU accelerated video decoding on Windows and easier website permissions. More detailed updates are available on the Chrome Blog.

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.

Occasionally, we issue special rewards for bugs outside of Chrome, particularly where the bug is very severe and/or we are able to partially work around the issue:

  • [Mac OS only] [$1000] [149904] High CVE-2012-5115: Defend against wild writes in buggy graphics drivers. Credit to miaubiz.

And back to your regular scheduled rewards, including some at the new higher levels:

  • [$3500] [157079] Medium CVE-2012-5127: Integer overflow leading to out-of-bounds read in WebP handling. Credit to Phil Turnbull.
  • [Linux 64-bit only] [$1500] [150729] Medium CVE-2012-5120: Out-of-bounds array access in v8. Credit to Atte Kettunen of OUSPG.
  • [$1000] [143761] High CVE-2012-5116: Use-after-free in SVG filter handling. Credit to miaubiz.
  • [Mac OS only] [$1000] [149717] High CVE-2012-5118: Integer bounds check issue in GPU command buffers. Credit to miaubiz.
  • [$1000] [154055] High CVE-2012-5121: Use-after-free in video layout. Credit to Atte Kettunen of OUSPG.
  • [145915] Low CVE-2012-5117: Inappropriate load of SVG subresource in img context. Credit to Felix Gr?bert of the Google Security Team.
  • [149759] Medium CVE-2012-5119: Race condition in Pepper buffer handling. Credit to Fermin Serna of the Google Security Team.
  • [154465] Medium CVE-2012-5122: Bad cast in input handling. Credit to Google Chrome Security Team (Inferno).
  • [154590] [156826] Medium CVE-2012-5123: Out-of-bounds reads in Skia. Credit to Google Chrome Security Team (Inferno).
  • [155323] High CVE-2012-5124: Memory corruption in texture handling. Credit to Al Patrick of the Chromium development community.
  • [156051] Medium CVE-2012-5125: Use-after-free in extension tab handling. Credit to Alexander Potapenko of the Chromium development community.
  • [156366] Medium CVE-2012-5126: Use-after-free in plug-in placeholder handling. Credit to Google Chrome Security Team (Inferno).
  • [157124] High CVE-2012-5128: Bad write in v8. Credit to Google Chrome Security Team (Cris Neckar).

Many of the above bugs were detected using AddressSanitizer.

The security issues in V8 have been fixed in v8-3.13.7.5.

We?d also like to thank miaubiz for working with us during the development cycle and preventing security regressions from ever reaching the stable channel. Rewards were issued.

This version also has a new Adobe Flash. More details can be found here.

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

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Dev Channel Update

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

  • Fixed BrowserFrameWin artifact on opaque to glass frame changes. (Issue: 156982)

  • Fixed a crash that could occur if the user closed a tab with an uncommitted search navigation. (Issue: 158201)

  • Fixed focus issue which does not change from Omnibox to Find in Page on mouseclick. (Issue: 158562)
  • Flash Mac: Fixed escape to exit fullscreen. (Issue: 155492)

  • Fixed crash when installing an extension and the browser window goes away. (Issue: 134194)

  • Ensure sidebar links are re-enabled when a confirmation dialog is closed. (Issue: 158912)
  • Fixed old Chrome version cleanup. (Issue: 75951)
  • Fixed memory leak in Chrome Windows. (Issue: 158931)
  • Fixed F4 inside <input type=time> should not open calendar picker. (Issue: 158482)
  • Fixed calendar picker can flicker when opened from the suggestion picker. (Issue 158608)

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

Beta Channel Update

The Beta channel has been updated to 24.0.1312.5 for Windows, Mac, Linux, and Chrome Frame. This build contains a slew of awesome developer features. More on what's new at the Chromium blog.

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

Does anyone know how to fix the slow browsing when ever a webpage has a background image? Using the latest dev-builds and it's this issue has been a part of those builds since a few builds back.

Dev Channel Update

The Dev channel has been updated to 25.0.1323.1 for Windows, Mac, Linux, and Chrome Frame. A full list of changes in this build is 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.

Jason Kersey

Google Chrome

Source: Google Chrome Releases blog

Chrome looks like started to get serious about 64-bit browser of Windows. Landed its configuration platform thingy on Chromium.

This bug is fixed: https://code.google.com/p/chromium/issues/detail?id=8606

Chrome looks like started to get serious about 64-bit browser of Windows. Landed its configuration platform thingy on Chromium.

This bug is fixed: https://code.google..../detail?id=8606

seems Google are more serious about 64bit windows builds than Mozilla are with there lack of " serious 64 bit builds . what i mean by " Serious " atleast Google will atleast officially support the browser unlike Mozilla

seems Google are more serious about 64bit windows builds than Mozilla are with there lack of " serious 64 bit builds . what i mean by " Serious " atleast Google will atleast officially support the browser unlike Mozilla

All well and good, but then Google has no 64bit voice and video plugin. What gives with that?

  • 3 weeks later...

Is anyone else getting the issue in dev where the cursor disappears when middle clicking to scroll and when hovering over images that can zoom?

Yes, and it's annoying as hell. I hope they fix it soon.

So I think Chrome Dev just updated today on my Mac, because now when I put it into Maximized (Full Screen) mode the bookmark bar vanishes, but address and tabs remain..

This is really annoying. I always keep it in it's maximized state so I can easily swipe between programs while keeping the desktop clean, or free for the few apps that don't support the feature..

Running 25.0.1354.0 dev

Is anyone else having issues with the "New Tab Page" and "Speed Dial 2"? For some reason, every time when I click on an empty space or outside of Chrome, a Google search page appears. Whenever I type in the search box, the "New Tab Page" or "Speed Dial 2" (depends on if I have SD 2 enabled) re-appear again.

Is anyone else having issues with the "New Tab Page" and "Speed Dial 2"? For some reason, every time when I click on an empty space or outside of Chrome, a Google search page appears. Whenever I type in the search box, the "New Tab Page" or "Speed Dial 2" (depends on if I have SD 2 enabled) re-appear again.

Switched back to the stable builds because this issue was getting way too annoying :/

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

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!