Today, we’re excited to make a nifty feature widely available in today’s new Chrome stable release: speech input through HTML.
Curious about how speech input can be used in real life? Here’s one example: Using Chrome, you can now translate what you say into other languages with Google Translate. If you’re translating from English, just click on the microphone on the bottom right of the input box, speak your text, and choose the language you want to translate to. In fact, you can even click on the “Listen” feature to hear the translated words spoken back to you!
Speech input through HTML is one of many new web technologies in the browser that help make innovative and useful web applications like Google Translate’s speech feature possible. If you’d like to check out more examples of applications built using the latest and greatest web technologies in the browser, you can check out more than 200 submissions by web developers onchromeexperiments.com. If you’re not already using Chrome, don’t forget to first download Chrome at google.com/chrome.
Some of the most compelling experiences on the web come when inspirations of old are brought to life with modern technologies. Last August, “The Wilderness Downtown” brought the wistful feeling of nostalgia to the browser as you run down the streets where you used to live in an HTML5music experience based on the Arcade Fire song “We Used to Wait.”
“3 Dreams of Black” is our newest music experience for the web browser, written and directed by Chris Milk and developed with a few folks here at Google. The song, “Black,” comes off the albumROME, presented by Danger Mouse & Daniele Luppi, featuring Jack White and Norah Jones on vocals and soon to be released on the record label Parlophone/EMI. ROME is inspired by Italian soundtracks from the 1960s and the classic Italian Western genre. In fact, the album was recorded with the original orchestra from Italian director Sergio Leone’s westerns (remember The Good, The Bad & The Ugly?).
“3 Dreams of Black” is a visual voyage through three dream worlds, told through rich 2D drawings and animations that are interspersed with interactive 3D sequences. At various points in this web experience, you can take control with your computer’s mouse and guide your journey through the unfolding narrative. You can even contribute to the dream by creating your own relics using a 3D model creator. Some of the best user creations will be integrated into the experience and become a part of others’ “3 Dreams” exploration.
In “3 Dreams in Black”, the browser is transformed into a theater for these lucid virtual dreams through WebGL, a new technology which brings hardware-accelerated 3D graphics to the browser. With WebGL in modern browsers like Google Chrome, you can interact with 3D experiences with no need for additional software. For curious web developers out there, we’ve made all the code completely open and available so that you can dig in, have a look around and try it out for yourself.
Because “3 Dreams in Black” is an experiment built with the latest web technologies, it requires a browser that supports WebGL like Chrome, and Windows Vista / Mac OS X 10.6 or above to help ensure that your computer has up-to-date graphics drivers. For those of you who may have hardware constraints, we’ve put together a short video that we hope will provide a glimpse into this unique experience. To explore these dreamscapes, visit www.ro.me.
Here a complete list of all startup switches in Chrome ad what they do:
// Allow third party content included on a page to prompt for a HTTP
// basic auth username/password pair.
const char kAllowCrossOriginAuthPrompt[] = "allow-cross-origin-auth-prompt";
// On ChromeOS, file:// access is disabled except for certain whitelisted
// directories. This switch re-enables file:// for testing.
const char kAllowFileAccess[] = "allow-file-access";
// Allow non-https URL for background_page for hosted apps.
const char kAllowHTTPBackgroundPage[] = "allow-http-background-page";
// Don't block outdated plugins.
const char kAllowOutdatedPlugins[] = "allow-outdated-plugins";
// Allows injecting extensions and user scripts on the extensions
// gallery site. Normally prevented for security reasons, but can be
// useful for automation testing of the gallery.
const char kAllowScriptingGallery[] = "allow-scripting-gallery";
// Specifies comma separated list of extension ids to grant access to local
// websocket proxy.
const char kAllowWebSocketProxy[] = "allow-websocket-proxy";
// Allow compositing on chrome:// pages.
const char kAllowWebUICompositing[] = "allow-webui-compositing";
// This prevents Chrome from requiring authorization to run certain widely
// installed but less commonly used plug-ins.
const char kAlwaysAuthorizePlugins[] = "always-authorize-plugins";
// Specifies that the associated value should be launched in "application" mode.
const char kApp[] = "app";
// Specifies that the extension-app with the specified id should be launched
// according to its configuration.
const char kAppId[] = "app-id";
// Override the apps checkout URL, which is used to determine when to expose
// some private APIs.
const char kAppsCheckoutURL[] = "apps-checkout-url";
// Specifying this flag allows the webstorePrivate APIs to return browser (aka
// sync) login tokens to be used for auto-login in the Web Store (normally they
// do not).
const char kAppsGalleryReturnTokens[] = "apps-gallery-return-tokens";
// The URL to use for the gallery link in the app launcher.
const char kAppsGalleryURL[] = "apps-gallery-url";
// The update url used by gallery/webstore extensions.
const char kAppsGalleryUpdateURL[] = "apps-gallery-update-url";
// Whether to always use the new app install bubble when installing an app.
const char kAppsNewInstallBubble[] = "apps-new-install-bubble";
// Disable throbber for extension apps.
const char kAppsNoThrob[] = "apps-no-throb";
// Whitelist of servers that Negotiate will generate delegated Kerberos tickets
// for.
const char kAuthNegotiateDelegateWhitelist[] =
"auth-negotiate-delegate-whitelist";
// HTTP authentication schemes to enable. This is a comma separated list
// of authentication schemes (basic, digest, ntlm, and negotiate). By default
// all schemes are enabled. The primary use of this command line flag is to help
// triage autentication-related issues reported by end-users.
const char kAuthSchemes[] = "auth-schemes";
// Whitelist of servers which NTLM and Negotiate can automatically authenticate
// with using the default credentials of the currently logged in user.
const char kAuthServerWhitelist[] = "auth-server-whitelist";
// The value of this switch tells the app to listen for and broadcast
// automation-related messages on IPC channel with the given ID.
const char kAutomationClientChannelID[] = "automation-channel";
// Causes the automation provider to reinitialize its IPC channel instead of
// shutting down when a client disconnects.
const char kAutomationReinitializeOnChannelError[] =
"automation-reinitialize-on-channel-error";
// When the option to block third-party cookies from being set is enabled,
// also block third-party cookies from being read.
const char kBlockReadingThirdPartyCookies[] =
"block-reading-third-party-cookies";
// How often (in seconds) to check for updates. Should only be used for
// testing purposes.
const char kCheckForUpdateIntervalSec[] = "check-for-update-interval";
// Tells chrome to load the specified version of chrome.dll on Windows. If
// this version cannot be loaded, Chrome will exit.
const char kChromeVersion[] = "chrome-version";
// Comma-separated list of SSL cipher suites to disable.
const char kCipherSuiteBlacklist[] = "cipher-suite-blacklist";
// Used with kCloudPrintFile. Tells Chrome to delete the file when
// finished displaying the print dialog.
const char kCloudPrintDeleteFile[] = "cloud-print-delete-file";
// Tells chrome to display the cloud print dialog and upload the
// specified file for printing.
const char kCloudPrintFile[] = "cloud-print-file";
// Specifies the mime type to be used when uploading data from the
// file referenced by cloud-print-file.
// Defaults to "application/pdf" if unspecified.
const char kCloudPrintFileType[] = "cloud-print-file-type";
// Used with kCloudPrintFile to specify a JSON print ticket for the resulting
// print job.
// Defaults to null if unspecified.
const char kCloudPrintPrintTicket[] = "cloud-print-print-ticket";
// Used with kCloudPrintFile to specify a title for the resulting print
// job.
const char kCloudPrintJobTitle[] = "cloud-print-job-title";
// The unique id to be used for this cloud print proxy instance.
const char kCloudPrintProxyId[] = "cloud-print-proxy-id";
// The URL of the cloud print service to use, overrides any value
// stored in preferences, and the default. Only used if the cloud
// print service has been enabled (see enable-cloud-print).
const char kCloudPrintServiceURL[] = "cloud-print-service";
// Comma-separated options to troubleshoot the component updater.
// Only valid for the browser process.
const char kComponentUpdaterDebug[] = "component-updater-debug";
// Causes the browser process to inspect loaded and registered DLLs for
// known conflicts and warn the user.
const char kConflictingModulesCheck[] = "conflicting-modules-check";
// The Country we should use. This is normally obtained from the operating
// system during first run and cached in the preferences afterwards. This is a
// string value, the 2 letter code from ISO 3166-1.
const char kCountry[] = "country";
// Causes the browser process to crash if browser threads are not responding for
// the given number of seconds.
const char kCrashOnHangSeconds[] = "crash-on-hang-seconds";
// Comma separated list of BrowserThreads that cause browser process to crash if
// the given browser thread is not responsive. UI,IO,DB,FILE,CACHE are the list
// of BrowserThreads that are supported.
//
// For example:
// --crash-on-hang-threads=UI,IO --> Crash the browser if UI or IO thread is
// not responsive.
const char kCrashOnHangThreads[] = "crash-on-hang-threads";
// Causes the browser process to crash if the number of browser threads that are
// responding is equal to the given number.
//
// For example:
// --crash-on-live=1 --> Crash if only one thread is responsive and all other
// threads are not responsive.
const char kCrashOnLive[] = "crash-on-live";
// Path to the inspector files on disk (allows reloading of devtool files
// without having to restart the browser).
const char kDebugDevToolsFrontend[] = "debug-devtools-frontend";
// Enables a frame context menu item that toggles the frame in and out of glass
// mode (Windows Vista and up only).
const char kDebugEnableFrameToggle[] = "debug-enable-frame-toggle";
// Enables support to debug printing subsystem.
const char kDebugPrint[] = "debug-print";
// Specifies the URL at which to fetch configuration policy from the device
// management backend. Specifying this switch turns on managed policy from the
// device management backend.
const char kDeviceManagementUrl[] = "device-management-url";
// Triggers a pletora of diagnostic modes.
const char kDiagnostics[] = "diagnostics";
// Replaces the audio IPC layer for
Today’s new Beta channel release brings big improvements to Chrome’s web platform capabilities, enabling developers to build more powerful and more immersive apps and games for the web.
First, we’re pleased to announce the integration of Native Client into Chrome. Native Client allows C and C++ code to be seamlessly executed inside the browser with security restrictions similar to JavaScript. Native Client apps use Pepper, a set of interfaces that provide C and C++ bindings to the capabilities of HTML5. As a result, developers can now leverage their native code libraries and expertise to deliver portable, high performance web apps.
Another cool feature is the Web Audio API, a new JavaScript API offering advanced audio capabilities. The Web Audio API supports audio effects such as room simulation and spatialization, allowing web developers to create even more interactive experiences and games. Here are some examples you can play with, but we’re looking forward to seeing what other people build!
Update 8/14: Native Client is currently only available for apps in the Chrome Web Store, but we plan to change this in the future. Keep an eye on the Chromium blog for updates.
Today’s world doesn’t slow down when you’re offline, so it’s a great feeling to be productive from anywhere, on any device, at any time. We recognize that offline access is important to many of you--especially for Chromebook users who spend most of their time living on the web. We talked about bringing this functionality to Google web apps at Google I/O 2011 and today, the Google Apps team is releasing Gmail Offline.
Gmail Offline is a Chrome Web Store app that helps you read, respond to, organize and archive email when you don’t have an internet connection. Google Calendar and Google Docs offline will also be rolling out over the next week. To get started using Google Calendar or Google Docs offline, just click the gear icon at the top right corner of the web app and select the option for offline access.
The great thing about web apps is that you can access all of your information on the go, and we’ve introduced ways to use Google Apps on a variety of devices like mobile phones and tablets. But it’s inevitable that you’ll occasionally find yourself in situations when you don’t have an Internet connection, like planes, trains and carpools. When we announced Chromebooks at Google I/O 2011, we talked about bringing offline access to our web apps, and now we’re taking our first steps in that direction. Gmail offline will be available today, and offline for Google Calendar and Google Docs will be rolling out over the next week, starting today.
Gmail Offline is a Chrome Web Store app that’s intended for situations when you need to read, respond to, organize and archive email without an internet connection. This HTML5-powered app is based on the Gmail web app for tablets, which was built to function with or without web access. After you install the Gmail Offline app from the Chrome Web Store, you can continue using Gmail when you lose your connection by clicking the Gmail Offline icon on Chrome’s “new tab” page.
Google Calendar and Google Docs let you seamlessly transition between on- and offline modes. When you’re offline in Google Calendar, you can view events from your calendars and RSVP to appointments. With Google Docs you can view documents and spreadsheets when you don’t have a connection. Offline editing isn’t ready yet, but we know it’s important to many of you, and we’re working hard to make it a reality. To get started using Google Calendar or Google Docs offline, just click the gear icon at the top right corner of the web app and select the option for offline access.
IT administrators can deploy Chrome Web Store apps to users en masse by setting up organizational policies for Chrome.
Today’s world doesn’t slow down when you’re offline and it’s a great feeling to be productive from anywhere, on any device, at any time. We’re pushing the boundaries of modern browsers to make this possible, and while we hope that many users will already find today’s offline functionality useful, this is only the beginning. Support for offline document editing and customizing the amount of email to be synchronized will be coming in the future. We also look forward to making offline access more widely available when other browsers support advanced functionality (like background pages).
With every Google Chrome release, we hope to bring new features and improvements that will make your life on the web speedier, simpler, and more secure. Today, we’re excited to introduce the integrated PDF viewer to the beta channel.
PDF is a popular file format that’s used for delivering documents on the web (such as the IRS W-4 tax form). To open a PDF document, you’d typically need to install additional software or a browser plug-in in order to view it in a web browser. With the integrated Chrome PDF viewer now available in Chrome’s beta, you can open a PDF document in Chrome without installing additional software. The PDF document will load as quickly and seamlessly as a normal web page in the browser.
Just like we do with web pages viewed in Chrome, we’ve built in an additional layer of securitycalled the “sandbox” around the Chrome PDF viewer to help protect you from malware and security attacks that are targeted at PDF files. For now, the Chrome PDF viewer is available only in the beta channel, but we look forward to adding more polish and features, as well as making it widely available in the stable channel soon.
This option is used to help in Development of Google chrome, It send your usage data to Google so that based on that they can further improve Chrome. But if you are worried about system performance you should disable it . To disable this go to tools menu > Options > Advanced and uncheck the check box which says Send usage data to Google….
Disable DNS Preload in Google Chrome
This will prevent Google chrome to keep DNS info in their cache. Most of time it is unnecessary if you have a good connection of at least 256kbps or more. It is recommended only for slow dial up connection or Mobile users who actually spend a lot f time in DNS query during browsing. to disable this select tools menu of Google Chrome and select “Options.” In the next window, go to the “Advanced” tab and uncheck the “Use DNS preload ….”
Disable anti-phishing filter
If you are advanced web user and you know how a phishing site look like or you know how to prevent from them you can disable this option. But if you are not at all comfortable working without phishing filters or don;t want to take risk you should keep it as it is . Disabling this not only saves your CPU time but also save your Internet bandwidth. This option can also be disabled from Tools Menu > Options > Advanced.
Removes navigational data regularly
All of the browsers cache the Navigation data and other info for faster access to web pages you frequently visit. But if your cache size is big or it contains very old pages which you hardly visit once or twice in a month it will start performing negative for you, as web pages will load faster but they Browsers perform worse when navigation data is saved. So it is important to remove navigational data frequently. To delete this in Chrome, go to Tools menu and choose the option “Remove navigation data” and choose “Delete data for this period” and not the option “All”. So it will remove old data and will keep recent data do this once in a week at least.
Disable Useless function which we don’t use normally –
To options that are mentioned below you need to edit the properties of Chrome shortcut which you are using to start the browser. To Change it, right click on the Chrome icon and choose “Properties.” this will open a windows with the “Shortcut” tab, in this tab there is a box called “Destination”. You have to change things in this box itself.
E.g. To disable Java box,
if you are using Windows Vista it should go like this — : “C:Users\AppDataLocalGoogleChromeApplicationchrome.exe -disable-java” and if you are using Windows XP: “C:Documents and Settings%username% Local SettingsApplication DataGoogleChrome.exe” The options which we are adding after the full path of chrome can be used one after the other leaving a space between. You don’t need to write the entire path every time you are using a new options. Here are the option which can be used -
Disable-dev-tools – This will disable Developers tool which is not used by a normal user for sure.
Disable-logging – This will disable looging of browser activity, This log files are useful only in case of Crash or Other error which prevent you from using browsers. if you are experiencing any such problem and need to know the reason you can enable this option. but in general you don’t need these log files. By disabling this you will certainly save CPU RAM and Hard disk space.
Disable-metrics-system – This option will disable gathering of Usage Statistics data. This is used by Google and we don’t need it any how so you can safely disable this option.
Disable-metrics-reporting – If you disabled Metrics system there is no point in keeping Metrics reporting On, as there won’t be any data to send across. Disable it for sure.
Disable-java – Java on the web is rarely used these days and it greatly slow downs your browsers performance. If you not running any online application which uses Java or Java Applets you can safely disable this feature. This will prevent you from playing number of Online Java Games though. (like Yahoo Games)
Disable-java script – This will disable all kinds of JavaScript from being run on the web pages you visit. This is not recommended at all as most of the sites these days are using some kind of JavaScript, to display pages. By Disabling JavaScript you will not be able to see these site properly and they will behave improprly. This is why disabling JavaScript is not recommended.
Disable-plugins – This will disable all plugins including Flash player and other media player. After applying this modification you won’t be able to see a lot of media sites properly including YouTube. If you understand impact of disabling this go ahead and do it otherwise don;t use this option.
Disable-images – This will disable all images on all Webpages you browse, if you are using low bandwidth conection like GPRS or Dial Up it will be very useful for you as it will save a lot of bandwidth for you. This will make your browser an text only browser. So be sure you need it that way before making these changes.
Google Chrome 8.0 recently graduated to the Dev Channel, but the development process needs to move extremely fast, if the final version of Chrome 7.0’s successor will be wrapped up and offered to users in approximately six weeks.
In this regard, Chrome 8.0 Beta is just around the corner. The Mountain View-based search giant is already gearing up to build the first Beta development milestone of Chrome 8.0.
For the time being however, early adopters and developers will need to content themselves with test driving the Dev channel release of Chrome 8.0, which went live on October 12th, 2010.
In a note shared with the developers working on Chrome, Google’s Jason Kersey emphasized the need to accelerate the efforts around the Beta Build.
The pressure put on devs to move as fast as possible is related to the six week major release process pace imposed by Google.
“As part of our goal to make the 6 week release cycle feasible, we are working to keep developers time spent on each release branch as short as possible,” Kersey stated.
“This allows for more feature and bug work on the trunk, and more coverage of the trunk with dev channels. To achieve this, I'm working to shorten the beta cycle for this release as much as possible.
“To do that means two things, less focus on non-blocker bugs, and (hopefully) quicker resolution of blocker bugs.”
Earlier this week, the Mountain View search giant managed to deliver the stable version of Chrome 7.0 right on time.
Users can now download Google Chrome 7.0.517.41 through both the Stable and Beta channels for Windows, Mac, and Linux.
At the same time, Google is also looking to the future and the company is already talking about Chrome 9.0.
Chromium 9.0 will be the first to be offered to early adopters, with Chrome 9.0 Dev and Beta following.
"We are aiming to get our first beta candidate in hand by the end of the week, and fixing this list of bugs is what blocks us from that," Kersey added.
Google confirm the release 9 of Chrome will add GPU Acceleration like Firefox 4 and Internet Explorer 9.
Some features expected in release 8.0 will be develop in next release of BigG browser
With the release of the first versions of Chrome 7, we noticed a subtle speed increase in graphics-heavy websites and suggested that Google is improving Chrome’s overall graphics performance. Our readers later found that GPU acceleration can already be manually activated in Chrome. Google has now officially confirmed that “there’s been a lot of work going on to overhaul Chromium’s graphics system” and that the browser will “begin to take advantage of the GPU to speed up its entire drawing model.”
It is the feature that Microsoft has been promoting for several months for its upcoming IE9 beta and a feature that is about to be activated in Firefox 4 Beta (5) early next month. Browser are beginning to take advantage of the multithreading capabilities of graphics processors to speed up their 2D and 3D performance. Google said that the functionality has been integrated in the “tip-of-tree Chromium” lately and the team “figured it was time for a primer.” Google says that it will be using the GPU to “speed up its entire drawing model, including many common 2D operations such as compositing and image scaling.”
The foundation of the GPU acceleration in Chrome is a new (modified) sandbox process called the GPU process. Via this process, Chrome can take graphics commands from the renderer process and send them to OpenGL or Direct3D. This approach enabled Google to separate the rendering of a web page into different independent layers, such as CSS, images, videos, and WebGL or 2D canvases. While some layers can be rendered on the GPU already, such as WebGL, others still depend on the CPU (text, images). Google says that blending the layers again by using the CPU would have erased all GPU speed gains, so Chromium now combines the layers by using the GPU. You can try this already simply by launching Chromium with the -enable-accelerated-compositing flag switch (make launch the browser from the command line menu and use the switch as an extension. Example: C:\Users\Wolfgang\AppData\Local\Google\Chrome\Application\chrome.exe -enable-accelerated-compositing)
Google said that it plans on offloading more and more work onto the GPU to “achieve impressive speedups”. Details are provided in a separate document on Google’s site.
The latest Nightly Builds of Chrome (Chromium) have also been equipped with a new “labs” feature that is apparently designed to deliver experimental features. It can be accessed via an about:labs command in the URL bar and shows, in this latest version (Chromium 7.0.508.0 Build 57738) vertically organized tabs on the left side of the screen, which resembles the navigation structure of a website. It’s an interesting concept if you have a widescreen monitor that can accommodate side tabs, but it may be a rather useless feature on smartphones or even netbooks. I personally like Mozilla’s Tab Candy (Panorama) approach to organize tabs much better.
At the actual version (2.0.172.33) ,Google Chrome, still have some bugs with Facebook.
The most troublesome for me is when I click "close" over a friend suggestion, in next friend suggestion I can't see friend name. This problem still remain until you refresh the page.
Sometimes Chrome seems hang up when a facebook tab is opened from a while. The notifications don't appear anymore and the chat don't work well. In this case you have to close the tab where Facebook is open.
I really don't know if this kind of issue are imputable to facebook ajax control (that doesnt respect standard) or to the immaturity of Google Chrome.
I still searching more information, and more user experince problem with FB.
Probabilly you have already read about the lot of new features this versione include, but i never hear about its new record on ACID3 Test. In fact Chrome 2.0.169.1 score in Acid Test is around 100!!
Another interesting features I have found and that isn't well-know, is now the search function works well inside page text box area too.
Other features can be found on official Google Chrome Release Blog here.
Anyway the most important include form autofill, full page zoom and autoscroll (both thanks to a new version of WebKit), and a cool new way to drag tabs out to get a side-by-side view (shown below).
All the rumors indicate that Google Chrome is exiting with new version 2.0.
Actually in Beta-version this release will include:
New version of WebKit, with lots of fixes and new features like full-page zoom, autoscroll, and CSS gradients and reflections.
New network code. Google Chrome now has its own implementation of the HTTP network protocol (we were using the WinHTTP library on Windows, but need common code for Mac and Linux).
Form Autocomplete.
Full-page zoom.
Autoscroll (rough implementation). Middle-click on a page to scroll the page in any direction.
A complete list of implemented features is available here
After 100 days of development and performance tuning Google Chrome can now leave the BETA tag and become official release.
All the user will get automatic updated to the latest release over the next few days, or download it here.
Note to Dev channel users: The Dev channel release will stay at 0.4.154.33. The current stable release is the same as the current Dev channel release without the Hotmail fix (which hasn't been tested enough to release to all users). An update is coming next week.
Bugs Fixed
[r6418] Allows Google Desktop links to launch Google Chrome as the default browser
[r6421] Fixes a crash when opening the Options dialog on 64-bit Windows (issue 49)
[r6464] Changes the accelerator keys for the Javascript debugger (Ctrl+Shift+L) and Javascript console (Ctrl+Shift+J). (Issues 3696, 5087)
[r6467] Fixes an issue with displaying unicode characters in some fonts. (Issue 5139)
[r6482] Fixes issues with composing mail and switching folders in Hotmail. Hotmail still does not properly recognize Google Chrome, so to use the site, you have to add the following to the shortcut you use to launch Google Chrome: (not in this release)
[r6492] Fixes the problem with 'Text zoom' being untranslated in non-English locales. (Issue 4591)
[r5556] Fix issue 343, Chinese Sogou input method loses first letter.
This release fixes the top issues we've heard about from people using the Beta release, especially with plugins (the programs that show video on sites like YouTube).
Wonderful! Google fix the freeze in Chrome caused by some plugins like Flash, very noise... now you can watch Yotube Videos and navigate on other windows without any problem!!!
Reading and scrolling PDF in Chrome is now very fast, unlike it was sice 0.2.149.30 release
I Think Google is doing a good Work.
Top Issues Fixed
Scrolling with laptop touchpads now works.
Improved performance and reliability for plugins (like Flash, Silverlight, QuickTime, and Windows Media). We fixed issues with video not loading, stopping after a second, and slowing down or freezing Google Chrome (100% CPU usage).
Fixed the 'chrome has crashed' message when you close a tab that was showing PDF using Adobe Reader 9.
We no longer store data from secure sites (they use https: and show a lock in the address bar) in your history. You can still search your history for the site's address, but not the contents on the page.
Improved performance and reliability for people who use web proxies (thanks to griffinz for the fixes).
Security Update
This release fixes an issue with address spoofing in pop-ups. A site could convince a user to click a link to open a pop-up window. The window's address bar could be manipulated to show a different address than the actual origin of the content. Security rating: Medium. This flaw could be used to mislead people about the origin of a web site in order to get them to divulge sensitive information. Disclosed by: Liu Die Yu of the TopsecTianRongXin research lab.
Changes to how things look and work
The New tab, New window, and New incognito window options moved from the 'Control the current page' menu to the 'Customize and control Google Chrome' (wrench) menu. Thanks to Szymon Piechowicz for the patch.
'New incognito window' always opens a new window. 'New window' always opens a new normal window. Both options are always visible on the wrench menu.
The spell checker works on text input fields and underlines misspelled words. You can now add words to the spell check dictionary so they are not shown as misspelled (right click on a misspelled word and choose 'Add to dictionary...').
The download behavior for files that could run programs (exe, dll, bat, etc.) has changed. These files are now downloaded to unconfirmed_*.download files. Google Chrome asks you if you want to accept the download. Only after you click Save is the unconfirmed_*.download file converted to the real file name. Downloads that you never confirm are deleted when Google Chrome exits.
Posts
