
Meanwhile, Emil Protalinski notes another ancient Microsoft standard that Chrome deprecated:Ĭhrome 37 will disable support for showModalDialog by default. If you click on the image, you can see the point that the post was actually trying to make. The image in the blog post got stretched, so that both look like poo. users should begin seeing better-looking fonts and increased rendering performance as we roll out DirectWrite, with no changes required by web developers. Graphics Device Interface (GDI).reflects the engineering tradeoffs of that time, particularly for slower, lower-resolution machines. The bug to get Chrome to support DirectWrite was filed in October 2009Ĭhrome 37 Beta.is due to graduate to the most-heavily used Stable channel in around six weeks. previously rendered text with which dates back to the mid-1980s. It's taken four and a half years but the engineering gurus.have finally improved how the browser renders text on Windows. MOREĪnd Seth Rosenblatt sharpens up the reporting: Users have long asked Google to make this switch, but the company says that it "required extensive re-architecting and streamlining." also now supports subpixel font scaling, which enables smooth animations of text between font sizes, and better support for touch events. Google released the latest beta version of its Chrome browser Windows fonts will now look better.because now supports Microsoft’s DirectWrite API. Your humble blogwatcher curated these bloggy bits for your entertainment. However, although you might get some important fixes, and the latest Chromium core, we also find the Dev version to be fairly unstable.In IT Blogwatch, bloggers initially eulogize: GDI API RIP. If you really feel you need the latest Chrome, this is for you.

If you do go down the Dev path, be prepared to enjoy a much less stable experience, although in return you’ll be testing cutting-edge features that won’t be available to other users for weeks if not months.Ĭhrome 82 is now in the Dev channel. Note that the Dev channel and should be used with some caution.

Unlike Canary, you can’t run Google Chrome Dev side-by-side with the stable, final version, although you could fashion your own clumsy workaround by running Chrome Dev alongside the portable version of Chrome. That said, Chrome Dev obviously remains a key part of the Chrome development cycle, as it’s the first release specifically designed for wider public consumption. It’s one step forward from the untested nightly builds of Chrome Canary, but it’s still a long way from the finished article, never mind the more reliable beta. Think of the Dev channel of Google Chrome as an alpha build, Chrome’s equivalent of Firefox Aurora.
