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

    • All these CEOs got the biggest boners thinking about firing employees for AI. Turned out it was just a wet dream.
    • And the fact that the majority of people from Poland are white European Christians while the people you are complaining about in post after post are not is just a coincidence... Every sentence in your post I am replying to is racist nonsense. None of it is actually based on any facts whatsoever. All immigrants are seeking a better life too. It's literally the only reason they would risk everything and leave their homes, families, and homeland. They are working and contributing to the economy too, as you even admit. They get the same benefits your partner did AND that YOU are eligible for as well. That is one of the key things of the EU and a mark of a civilization. That is the definition of a society where everyone is given a chance, treated equally and fairly, and is judged by the content of their character, not their different skin color or which version of ignorant superstitious nonsense their parents lied about as children. Racists around the world said the same things about the Irish and Jews and Poles (like your partner) and...every other immigrant movement over the centuries. What's your family's heritage, by the way? Were your ancestors lied about with racist fearmongering crapola by self-entitled locals the same way as you are now? If someone like that said the same things about all people from Poland, like your partner, would they be right? Or would you want them to judge your partner based on who they actually were, not where they just happened to come from?
    • Again, this is an irrelevant attempt to attack the messenger. The truth does not require any justification.
    • Removed the blue and underline as you did not post a link. This would also  be considered spamming.
    • Why it's almost impossible to produce a smartphone in the United States by Hamid Ganji If you look at the back of some Apple products, you can see the famous phrase “Designed by Apple in California, Assembled in China.” This phrase appears on products from one of the largest smartphone brands in the United States. These products are designed in the U.S., but their manufacturing takes place in China, India, Vietnam, or even Brazil. But why can’t Apple, as one of the largest American tech companies, produce its iPhones on U.S. soil? The idea for this topic came to me after the Trump Foundation launched a smartphone called the T1 and claimed that it was designed and built with American values in mind. However, this claim did not last long, as it was revealed that Trump’s phone was actually a rebranded HTC U24 Pro, with only a gold case and minor internal component changes. You see? Even a phone that is supposed to represent American values is manufactured in China. With a gross domestic product (GDP) exceeding $32 trillion, the United States is currently the world’s largest economy, while China ranks second with around $20 trillion. On the other hand, the United States is by a wide margin the global leader in various technological fields, and American companies spend hundreds of billions of dollars annually on research and development. From Apple and Google to Microsoft, Lockheed Martin, Boeing, and others, American tech and industrial giants lead their foreign competitors in many sectors. The United States also has no shortage of smartphone brands. Apple, Google, and Motorola are among the major brands in the smartphone market, collectively holding a significant share. However, the vast majority of their products are manufactured outside the United States. So why is it that the world’s largest economy, home to the most advanced technology companies and industrial powers, cannot produce a smartphone on its own soil? Let’s explore this question together. Even threats to impose tariffs won’t work After Trump entered the White House as the 47th President of the United States, his administration adopted strict tariff policies. One of these policies was the imposition of a 25% tariff on smartphones manufactured outside the United States. Trump said he “had a little problem” with Apple CEO Tim Cook over producing smartphones outside the U.S. So he thought that threatening a 25% tax on imported phones might force Apple to bring manufacturing back to the United States. “I have long ago informed Tim Cook of Apple that I expect their iPhones that will be sold in the United States of America will be manufactured and built in the United States, not India, or anyplace else,” Trump wrote on Truth Social. Image via The White House Although Apple currently manufactures some of the iPhone’s chips in the United States with TSMC's help, it still shows no willingness to shift full iPhone production to the country. At the time, renowned Apple supply chain analyst Ming-Chi Kuo wrote on X, “In terms of profitability, it’s way better for Apple to take the hit of a 25% tariff on iPhones sold in the US market than to move iPhone assembly lines back to the US.” However, manufacturing a smartphone in the United States is not as easy as it might seem, and many technical and economic barriers are involved. The lack of necessary manufacturing hubs There is a clear reason why many companies prefer to manufacture their products in China. China has established itself as the main global manufacturing hub for international companies, and over the past few decades, large contract manufacturers have emerged there, allowing companies like Apple to outsource production. One such example is Foxconn, which also manufactures some Apple products in India. Building the infrastructure required to produce smartphones in the United States would require tens of billions of dollars in new investment. Factories would need to be built, essential manufacturing equipment would have to be installed, and, most importantly, a skilled workforce capable of operating these systems would need to be recruited and trained. The United States currently lacks the core infrastructure needed to manufacture smartphones, and for this reason, many companies prefer to outsource production to Chinese contractors rather than spend tens of billions of dollars to build that infrastructure, which is significantly more economically efficient. Additionally, building such infrastructure in the United States could take up to a decade, ultimately leading to a significant increase in the product's final price for consumers. Shortage of trained labor in the U.S. compared to China Decades of serving as a global manufacturing hub have allowed China to build a massive talent pool in the production sector that is almost unmatched worldwide. Today, if a company chooses to manufacture its products in China, it can be confident that the workers involved in production have years of experience in their respective roles and are capable of producing high-quality goods with minimal errors. Even if we assume that tens of billions of dollars were invested in building smartphone manufacturing infrastructure in the United States, finding skilled workers would remain highly challenging. Apple CEO Tim Cook visiting the iPhone 6 assembly line in China in 2014. Image: Tim Cook on X In a 2015 interview on CBS’s 60 Minutes, Tim Cook said the main reason Apple isn’t producing in the US is a lack of skills. "China put an enormous focus on manufacturing, in what you and I would call vocational kind of skills. The US over time began to stop having as many vocational kinds of skills. I mean you could take every tool and die maker in the United States and probably put them in the room that we're currently sitting in. In China you would have to have multiple football fields,” Cook said. Also, in 2017, at the Fortune Global Forum in Guangzhou, Cook once again emphasized the importance of highly skilled Chinese workers. “China has moved into very advanced manufacturing, so you find in China the intersection of craftsman kind of skill, and sophisticated robotics and the computer science world. That intersection, which is very rare to find anywhere, that kind of skill, is very important to our business because of the precision and quality level that we like. The thing that most people focus on if they’re a foreigner coming to China is the size of the market, and obviously, it’s the biggest market in the world in so many areas. But for us, the number one attraction is the quality of the people,” Apple CEO said. Higher labor costs in the United States Producing almost any product in the United States is more expensive than in many other countries, and one of the main reasons is the higher cost of labor in the U.S. According to the Bureau of Labor Statistics, median weekly earnings of full-time workers in the United States were $1,235 in the first quarter of 2026. Meanwhile, the average annual salary in China's private sector in 2025 was RMB 71,590 (US$9,961). In many parts of the world, the weekly wage of an American worker is equivalent to several months of income. Another important factor to consider is that in the United States, the workforce capable of working on a smartphone assembly line is highly specialized and therefore commands higher-than-average wages. According to an estimate by Bank of America, producing an iPhone in the U.S. is technically possible, but “iPhone cost can increase 25% purely on higher labor cost in the U.S.” However, this 25% increase applies only if final assembly is performed in the United States while components are still sourced from China or elsewhere. In this case, the price of a base iPhone would rise from $799 to around $1,000. But in another scenario, if Apple were to produce the required components for the iPhone within the United States, production costs could increase by more than 90%. Trump’s dream for a “Made in the USA” iPhone might never come true In a free-market capitalist economy, one of the primary responsibilities of any CEO is to maximize profit. Using Apple as an example, Tim Cook’s role is to maximize the company’s profits so that it can fund research and development for new products and invest in areas such as artificial intelligence, while also keeping shareholders satisfied. Therefore, it is entirely understandable that Apple would choose not to bring its manufacturing back to the United States and instead keep production in countries where labor is cheaper, and products can be manufactured at a lower cost, thereby maximizing its profit margins. What is your opinion about manufacturing smartphones in the United States? If you are an American citizen, would you be willing to pay hundreds of dollars more for a smartphone made domestically in the USA? Let us know in the comments.
  • Recent Achievements

    • Conversation Starter
      jessse3334 earned a badge
      Conversation Starter
    • Reacting Well
      JuvenileDelinquent earned a badge
      Reacting Well
    • One Month Later
      Excellence2025 earned a badge
      One Month Later
    • Week One Done
      Excellence2025 earned a badge
      Week One Done
    • Week One Done
      flexorcist earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      +Edouard
      196
    3. 3
      PsYcHoKiLLa
      153
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      65
  • Tell a friend

    Love Neowin? Tell a friend!