Home Web Internet Chrome gets high-resolution screen support on Windows, too

Chrome gets high-resolution screen support on Windows, too


As windows machines apply in Apple’s Retina display footsteps, Google is constructing HiDPI support into its Chrome browser. The browser developer marked HiDPI fortify in home windows as fixed on Tuesday night, although it is weeks far from arriving within the secure model of Chrome. It can be at present scheduled for release in Chrome 30; the present stable version is Chrome 28, and Google releases new variations about every six weeks.

Google Chrome logo

High-decision monitors have more dots per inch than typical screens; for this reason, the label HiDPI, which is nice for crisper pix and textual content. Then again, programmers should adapt pix elements corresponding to icons and browser tabs whose designs are measured with the aid of a set selection of pixels. Otherwise, they can be both unusably small or unpleasantly coarse and pixelated.

HiDPI makes stronger isn’t but complete — some font work continues to be executed, for instance — however, people eager to investigate the brand new feature now can. “If you want to try it out, run the present canary build, and add the flag –excessive-dpi-strengthen=1,” a remark in the characteristic tracker stated.

In view that Google first released it in 2008, Chrome has carved out a stronghold in the browser market. Google makes use of it to drive net advancements corresponding to SPDY for faster communications between net browsers and servers, QUIC for sooner internet communications overall, and Chrome Packaged Apps for net apps that work extra like native apps. And it also makes a bundle of cash off the mission because with searches through Chrome; Google would not pay any companions such as Mozilla or AOL for a component of ensuing search-advert earnings.

Related More Articles

Google works to make Chrome as stable as it will probably. Also, on Tuesday, Google released a new incarnation of Chrome 28 that fixes a lot of safety issues. Bounty payments linked to these fixes included a “unique reward” of $21,500 for Andrey Labunets’ work determining two vulnerabilities, CVE-2013-2879 and CVE-2013-2868.