Want a super fast browser? So do I. Want a web application and full HTML5 implementation? So do I. But you have to wait. And in some aspects, and wait a long time, because the work is titanic.
Usually in software development, the moment is right when programmers have to divert their attention from adding cool new technology to ensuring that the entire functionality is fully functional. This moment, called the code freeze, came in the sixth "milestone" of Google Chrome.
Google believes in the constant updating of its browser and oppression of its line, demonstrating active work, both in development and in advertising. Chrome managed to briskly break into the top three dominant browsers, making (not yet very serious) competition for Internet Explorer and Mozilla Firefox, as well as bypassing browsers from Opera Software ASA and Apple by the number of users. And this is just two incomplete years of the browser. (According to various sources, Google Chrome takes from 7 to 9 percent of the global market
It so happens that, having missed the subway train, you will not wait long for the next one, but you still have to wait until the arrival of the new train. So it happened with some features of Google Chrome. They simply did not have time for a train called Chrome 6 and they still have to wait for Chrome 7.
Print support was one of the relatively weaknesses of the Google Chrome browser compared to other browsers that have been on the market for web browsers longer, but Google has worked hard to catch up and outrun competitors. There were also failures in the form of poor implementation of printing of the selected fragment of the text, there were also successes, such as unsuccessful attempts to hack the browser at Pwn2Own competitions.
As for printing problems, there is a consolation for Windows users. The developers have fixed a bug
, and the change will be included in the release of Chrome 6, but Mac and Linux users will have to wait for
version 7, when the entire print function will be redone. Long requests for the print preview function had an effect on the developers, and the function will be implemented, which is very joyful. Given the rate of release of new versions, it will happen relatively soon. Fall-winter 2010.And why is Chrome 6?
So why did Google decide to upgrade the Chrome version? Are there really no new chips and opportunities, but only the “remaining to wait for the new train” functions? Of course there is, and then for the sake of which to make a fuss from the mass of versions? So, unlike the 5 version of Chrome 6 will be:
* Sync extensions
. Now you do not have to painfully delve into the immense, poorly structured official directory of extensions in the search for their favorite addonchikov. I loaded the browser and started the sync. Great!
* Accelerate the output of images in SVG format
* Combine the browser settings buttons and work with the page
. Fashion trend in recent times. Both Opera 10 and Mozilla Firefox 4 practice a one-button model. Is it convenient? Solve everyone.
* Synchronize your browsing history
. I think this is a useful feature, although some browser users dream of the password synchronization feature.
* Optimize the scaling of
high-quality high-resolution images. Users of multi-core processors will notice this especially well.
1. Support HTML5Google Chrome 5.0.375.99 Stable
Progress is evident. Of course, much will be corrected and supplemented by the transition of the browser to the Stable branch, but this is the trend.
* A lot of money
for found vulnerabilities. $ 3133.7
will not hurt anyone.
In general, a sufficient set to assign a new tsiferki in the version number.What else will not see in Chrome 6?
* The function of moving the tab bar
from top to side did not have time to "finish." You can run the feature in Windows with the --enable-vertical-tabs option, but developers warn that this feature is in active development, so it may be unstable.
* Support for full-screen video playback in HTML5
. So far, Google Chrome is not able to, but it is very keen on the full-fledged work of video with HTML5, because Google clearly does not burn with desire to depend on third-party plug-ins (for example, Adobe Flash).
* Implement NativeClient
for faster web applications. Of course, to say that this is done exclusively for the browser prematurely, because, as you know, Google is intensively working on the operating system Chromium OS, but still it would be desirable to have a browser-OS hybrid (with a roll towards the browser).
* A number of quite interesting features.
Delicious features, is not it?
Given the long lull in the stable and beta branches of Google Chrome updates, build 6 versions will soon fall into these channels. In the meantime, there are only dev-releases of Google Chrome 6
. The browser warfare is in full swing.Sources
:Chrome 6 featuresGoogle Chrome Dev ReleasesGoogle Chromium blog