Google's Chrome web browser has seen one more update on the dev channel. The new version is 4.0.220.1 furthermore it bring down a series of fixes, notes Jonathan Conradt, Engineering Program Manager. The new-fangled flavor has the Native Client as a built-in feature, which happens for the very first time as quickly as it comes to the Windows version of Chrome moreover there is also a series of Extensions APIs incorporated with this release.
The new Google Chrome 4.0.220.1 dev has new features also fixes for all platforms, together with the elimination of “Remove Item” from download item context menu (which is no longer needed as the shelf removes all completed and canceled items on close), or the truth that Omnibox now understands Zeroconf .local hosts. Once it comes to the Windows version of the browser, the noteworthy change is that the Native Client is currently built into the renderer.
One thing that must be noted at this time is that the Native Client is disabled by default, and that users will have to do quite a few actions to enable it. After downloading Google Chrome as well as registering tot hr dev channel, “launch Google Chrome from the command line, adding --internal-nacl.
If you are in the directory that contains chrome.exe (somewhat like C:\Documents and Settings\me\Local Settings\Application Data\Google\Chrome\Application) and your command be supposed to look like this: chrome.exe --internal-nacl. Warning: Currently, using --internal-nacl, this will disable the Google Chrome sandbox. This is interrelated to a bug that we look forward to fix soon, but for now, we suggest to run Google Chrome with this flag simply for testing Native Client and it is not for regular web browsing.” Additional details can be found here.
As for the changes with extensions, the list shows extensions menu item currently in “wrench” menu; the occurrence of Browser Actions; extension packing has been implemented for Linux; the toolstrip dragging is being limited to extension shelf; when the “ask for destination” choice has been set in download options, the themes as well as the extensions will install; a crash with non-extension iframe has been rigid; initial i18n API included; at present the content scripts are enabled to see their own functions in setTimeout.
The new Google Chrome 4.0.220.1 dev has new features also fixes for all platforms, together with the elimination of “Remove Item” from download item context menu (which is no longer needed as the shelf removes all completed and canceled items on close), or the truth that Omnibox now understands Zeroconf .local hosts. Once it comes to the Windows version of the browser, the noteworthy change is that the Native Client is currently built into the renderer.
One thing that must be noted at this time is that the Native Client is disabled by default, and that users will have to do quite a few actions to enable it. After downloading Google Chrome as well as registering tot hr dev channel, “launch Google Chrome from the command line, adding --internal-nacl.
If you are in the directory that contains chrome.exe (somewhat like C:\Documents and Settings\me\Local Settings\Application Data\Google\Chrome\Application) and your command be supposed to look like this: chrome.exe --internal-nacl. Warning: Currently, using --internal-nacl, this will disable the Google Chrome sandbox. This is interrelated to a bug that we look forward to fix soon, but for now, we suggest to run Google Chrome with this flag simply for testing Native Client and it is not for regular web browsing.” Additional details can be found here.
As for the changes with extensions, the list shows extensions menu item currently in “wrench” menu; the occurrence of Browser Actions; extension packing has been implemented for Linux; the toolstrip dragging is being limited to extension shelf; when the “ask for destination” choice has been set in download options, the themes as well as the extensions will install; a crash with non-extension iframe has been rigid; initial i18n API included; at present the content scripts are enabled to see their own functions in setTimeout.
No comments:
Post a Comment