Google has begun rolling out version 62 of its Chrome browser to the Mac, Windows, and Linux platforms. The new version includes changed security behaviors and new features for developers. The new version includes changed security behaviors and new features for developers.
Hey Chrome family, Happy New Year! Chrome 56 will be updating shortly to your device and you should see a notice in the coming weeks to update to the latest version. See the list below of some of the exciting changes we have in this release: Desktop:. Print scaling. We’ve heard from a number of you and we’re glad to let you know that Chrome now allows print scaling!
Now when you open up Chrome’s print preview, you can print web pages with the contents (text and images) scaled to be larger or smaller. You can also print PDFs with the pages scaled bigger or smaller.
You can change the print scaling by opening print preview (More print) click on “more settings” adjust the scale by typing in a number higher or lower than 100. Note this feature will be slowly rolling out to users and may not be available for everyone as Chrome 56 releases. Changes to website certificate handling. As announced back in, Chrome will no longer treat SHA-1 certificates as secure and websites with SHA-1 certificates will trigger a “Your connection is not private” warning in Google Chrome. SHA-1 is a cryptographic algorithm that dates back to 1995 and is no longer considered secure. We encourage any website developer still running SHA-1 certificates to update to SHA-2 certificates immediately in order to reduce any disruption to their site or service.
More details are included in our. Note Chrome 56 will also stop trusting certificates issued by WoSign and StartCom after October 21 st 2016 in response to from last year by these certificate providers. Updates to the address bar (aka omnibox) for HTTP pages with a password or credit card forms.
We think it should be easy to browse the web securely - so we've made a change to make it easier to tell when you're viewing non-secure pages that ask for especially sensitive information (in particular, passwords or credit cards). If a page is HTTP (aka non-secure), it means your sensitive data could potentially be stolen by attackers. In Chrome 56, HTTP pages that have a password or credit card form will display 'Not secure' in the address bar (aka omnibox). We've made this warning more visible so that you can stay informed when making security decisions online. If you run into this issue when visiting a site, try inserting an 'S' at the end of “HTTP” in the URL (see for more info), or try reaching out to the developer of the site and encourage them to update to the more secure HTTPS to keep your information safer. Note: Websites using HTTPS will display “Secure” in the address bar. Android:.
Spell check now available. Previous versions of Chrome for Android used the built-in Android OS auto-correct function for spelling, but this latest update now provides a separate spell check feature within Chrome for Android. Updates to the new tab page. We’ve made quite a few changes to the new tab page with this latest update. You can see all of the latest updates below:.
Downloads now on the new tabs page. We’ve now made it even easier to access your downloaded articles and downloaded files directly from the new tab page.
Simply scroll down to the “Downloads” section. Swipeable sections. Do you feel like “Downloads”, “Recent Bookmarks” or “Articles for You” are not relevant to you?
Or just done for now? You can now not only swipe left or right to dismiss these suggestions but also swipe entire sections to remove them from your new tab page. Long press actions. You can long press on articles to download it for offline viewing, open in a new tab, open in an incognito window, or remove from the list. Offline badges for offline articles. If you’ve previously saved an article to your device for offline viewing (see above), an icon with the underlined check mark will display near the article to indicate you can read it offline.
See more relevant articles. Want to see more relevant articles? Tap the “more” button at the bottom of the articles to reveal more news for you. IOS:. QR code scanner integration for Chrome for iOS.
Are you a fan of scanning QR codes? No need to have a separate QR code reader app-in Chrome 56 we’ve now integrated a QR code reader directly into Chrome. To access it, you can:. 3D touch on the Chrome logo from your home page and select “Scan QR Code”. Swipe left or down from the home screen to enable Spotlight and type “QR” in the search box to find this feature in Chrome.
Note that this feature only works on devices that support Spotlight Actions. This feature will currently not work on following devices but we’re looking into addressing this in the future: iPhone 4s, iPad 2, iPad (3rd generation), iPad Mini, and iPod Touch (5th generation). This feature also works on scanning bar codes! If you have any questions or feedback about the features above, please let us know! Best, Kameron and the Chrome team Edit: This topic is now outdated as we're several months out of Chrome 56 and this version is now outdated so this topic has been locked. We'd recommend updating to the latest version (57+) if you're running into issues and post another topic if you need further help or have questions. (ไม่รู้จัก) 2/2/2017, 12:32 น.
Stefan vd 2/2/2017, 14:25 น. 错误详情： KSOutOfProcessFetcher timeout while waiting for fetch. com.google.UpdateEngine.CommonErrorDomain:1502 - ' - 'KSOutOfProcessFetcher.m:705' KSServerUpdateRequest fetch failed. (productID: com.google.Chrome) com.google.UpdateEngine.CoreErrorDomain:702 - ' (KSOutOfProcessFetcher timeout while waiting for fetch.
' com.google.UpdateEngine.CommonErrorDomain:1502) KSOutOfProcessFetcher timeout while waiting for fetch. com.google.UpdateEngine.CommonErrorDomain:1502 - ' - 'KSOutOfProcessFetcher.m:705' KSServerUpdateRequest fetch failed. (productID: com.google.Chrome) com.google.UpdateEngine.CoreErrorDomain:702 - ' (KSOutOfProcessFetcher timeout while waiting for fetch.
' com.google.UpdateEngine.CommonErrorDomain:1502). On my print preview there is no scaling option available. The list of options go as: Destination, Pages, Copies, Layout, Paper Size, Margins, Quality, Options. But somehow overnight my scale has been adjusted and a document that I print 50x a day for work is now on two pages, at larger scale, and cutting off vital information. The only way to have all info fit onto one page is to change the output of paper to 11x17. Which will not work for my business.
How can this be resloved and when will my chrome have the scaling option? How can I disable PDF's from opening in Chrome? When I go to chrome://plugins, the 'Always allowed to run' box is checked and locked so I can't un-check it. I also went to chrome://flags to enable NPAPI and it's gone! I've been searching for answers and all I can find is NPAPI is now disabled / obsolete. I think it's COMPLETELY unacceptable that I cannot set my downloaded PDF's to open in Acrobat Pro. I need Acrobat for work and it was keeping my PDF's on a separate monitor from Chrome as I am cross referencing data from my server and PDF docs on different monitors all day long.
I am not happy right now. No, I don't want to right click and save as. I want my single click opens in Acrobat back! Jameswinchester3487 10/2/2017, 11:11 น. I'm super excited for print scaling!
In a way, I can now understand (partially) why they removed the previous 'Simplify Page' option under Print Settings (whose absence is still missed and collateral grievances often revisited, especially when a scrolling banner ad appears on every single printed page blocking any text within 1.5 inches of the regular page margins-a hindrance a simple checkbox next to 'Simplify Page' would have once easily solved - but I digress) so I'm glad to see progress in the print department! I'm also stoked for the save for offline viewing for android but am wondering a couple things both related and unrelated. Regarding Chrome 56: For the past two weeks or so, two of my often used email accounts are showing as 'not secure' (Windows Live Mail and Yahoo Mail) on both my home pc and my office pc (both machines are running Windows 10), while my gmail account appears to be secure.
In addition, many frequently visited websites are also 'not secure' now. This seemingly happened overnight as it was never a issue I noticed before. I've been running full anti-virus scans and malware scans every day with McAfee Total Protection (home pc), Kaspersky Internet Security(office pc) and Malwarebytes (both pc's) but everything comes up clean. Both machines have Chrome 56.0.2924.87. But when when browsing with Microsoft Edge the email accounts and websites appear to be secure. Whats going on with the latest Chrome version and these email accounts/websites?
Chrome 56 Rolling Out For Macbook Pro
Don Nadeau 21/2/2017, 5:40 น. Well, I scrubbed my laptops in the same manner, including Norton Power Eraser, GMER, TDSS Killer, on and on, coming up all clean!
I tried Chrome 56, Firefox, Edge/Bing, all insecure for Bank of America site, but working properly on all other HTTPS sites I use for banking. Lastly, I did a hard reset on my FIOS modem, my ASUS router, my enGenius AP, and even my switch.
BofA site still not secure and inaccessible. The error message is 'Timed Out'. Pulling my hair out since I own the company and need to use the online banking.
PS: I went to Starbucks and BA website worked fine! So it is somewhere here in my office. (ไม่รู้จัก) 21/2/2017, 9:20 น. Shafiqul Islam 22/2/2017, 7:53 น. Infinity light 22/2/2017, 7:55 น. Chris Ursich 22/2/2017, 11:37 น.
Hey Chrome family, Happy New Year! Chrome 56 will be updating shortly to your device and you should see a notice in the coming weeks to update to the latest version. See the list below of some of the exciting changes we have in this release: Desktop:. Print scaling. We’ve heard from a number of you and we’re glad to let you know that Chrome now allows print scaling! Now when you open up Chrome’s print preview, you can print web pages with the contents (text and images) scaled to be larger or smaller.
You can also print PDFs with the pages scaled bigger or smaller. You can change the print scaling by opening print preview (More print) click on “more settings” adjust the scale by typing in a number higher or lower than 100. Note this feature will be slowly rolling out to users and may not be available for everyone as Chrome 56 releases. Changes to website certificate handling.
As announced back in, Chrome will no longer treat SHA-1 certificates as secure and websites with SHA-1 certificates will trigger a “Your connection is not private” warning in Google Chrome. SHA-1 is a cryptographic algorithm that dates back to 1995 and is no longer considered secure. We encourage any website developer still running SHA-1 certificates to update to SHA-2 certificates immediately in order to reduce any disruption to their site or service.
More details are included in our. Note Chrome 56 will also stop trusting certificates issued by WoSign and StartCom after October 21 st 2016 in response to from last year by these certificate providers.
Updates to the address bar (aka omnibox) for HTTP pages with a password or credit card forms. We think it should be easy to browse the web securely - so we've made a change to make it easier to tell when you're viewing non-secure pages that ask for especially sensitive information (in particular, passwords or credit cards). If a page is HTTP (aka non-secure), it means your sensitive data could potentially be stolen by attackers. In Chrome 56, HTTP pages that have a password or credit card form will display 'Not secure' in the address bar (aka omnibox).
We've made this warning more visible so that you can stay informed when making security decisions online. If you run into this issue when visiting a site, try inserting an 'S' at the end of “HTTP” in the URL (see for more info), or try reaching out to the developer of the site and encourage them to update to the more secure HTTPS to keep your information safer.
Note: Websites using HTTPS will display “Secure” in the address bar. Android:. Spell check now available. Previous versions of Chrome for Android used the built-in Android OS auto-correct function for spelling, but this latest update now provides a separate spell check feature within Chrome for Android. Updates to the new tab page. We’ve made quite a few changes to the new tab page with this latest update.
You can see all of the latest updates below:. Downloads now on the new tabs page. We’ve now made it even easier to access your downloaded articles and downloaded files directly from the new tab page. Simply scroll down to the “Downloads” section. Swipeable sections. Do you feel like “Downloads”, “Recent Bookmarks” or “Articles for You” are not relevant to you? Or just done for now?
You can now not only swipe left or right to dismiss these suggestions but also swipe entire sections to remove them from your new tab page. Long press actions.
You can long press on articles to download it for offline viewing, open in a new tab, open in an incognito window, or remove from the list. Offline badges for offline articles. If you’ve previously saved an article to your device for offline viewing (see above), an icon with the underlined check mark will display near the article to indicate you can read it offline. See more relevant articles.
Want to see more relevant articles? Tap the “more” button at the bottom of the articles to reveal more news for you. IOS:. QR code scanner integration for Chrome for iOS. Are you a fan of scanning QR codes?
No need to have a separate QR code reader app-in Chrome 56 we’ve now integrated a QR code reader directly into Chrome. To access it, you can:.
3D touch on the Chrome logo from your home page and select “Scan QR Code”. Swipe left or down from the home screen to enable Spotlight and type “QR” in the search box to find this feature in Chrome. Note that this feature only works on devices that support Spotlight Actions.
This feature will currently not work on following devices but we’re looking into addressing this in the future: iPhone 4s, iPad 2, iPad (3rd generation), iPad Mini, and iPod Touch (5th generation). This feature also works on scanning bar codes! If you have any questions or feedback about the features above, please let us know! Best, Kameron and the Chrome team On Thursday, February 2, 2017 at 10:04:49 PM UTC+5:30, Kameron M wrote. Hey Chrome family, Happy New Year!
Chrome 56 will be updating shortly to your device and you should see a notice in the coming weeks to update to the latest version. See the list below of some of the exciting changes we have in this release: Desktop:.
Print scaling. We’ve heard from a number of you and we’re glad to let you know that Chrome now allows print scaling! Now when you open up Chrome’s print preview, you can print web pages with the contents (text and images) scaled to be larger or smaller.
Chrome 56 Download
You can also print PDFs with the pages scaled bigger or smaller. You can change the print scaling by opening print preview (More print) click on “more settings” adjust the scale by typing in a number higher or lower than 100.
Note this feature will be slowly rolling out to users and may not be available for everyone as Chrome 56 releases. Changes to website certificate handling. As announced back in, Chrome will no longer treat SHA-1 certificates as secure and websites with SHA-1 certificates will trigger a “Your connection is not private” warning in Google Chrome. SHA-1 is a cryptographic algorithm that dates back to 1995 and is no longer considered secure.
We encourage any website developer still running SHA-1 certificates to update to SHA-2 certificates immediately in order to reduce any disruption to their site or service. More details are included in our. Note Chrome 56 will also stop trusting certificates issued by WoSign and StartCom after October 21 st 2016 in response to from last year by these certificate providers. Updates to the address bar (aka omnibox) for HTTP pages with a password or credit card forms. We think it should be easy to browse the web securely - so we've made a change to make it easier to tell when you're viewing non-secure pages that ask for especially sensitive information (in particular, passwords or credit cards).
If a page is HTTP (aka non-secure), it means your sensitive data could potentially be stolen by attackers. In Chrome 56, HTTP pages that have a password or credit card form will display 'Not secure' in the address bar (aka omnibox). We've made this warning more visible so that you can stay informed when making security decisions online. If you run into this issue when visiting a site, try inserting an 'S' at the end of “HTTP” in the URL (see for more info), or try reaching out to the developer of the site and encourage them to update to the more secure HTTPS to keep your information safer.
Note: Websites using HTTPS will display “Secure” in the address ba Suhan Shetty 2/3/2017, 2:15 น. So I've updated my Chromebook to version 56, and ever since, I cannot access or watch YouTube videos on my Chromebook. My browser, even in Incognito mode, is treating YouTube like an SHA-1. It really bothers me, because I have to watch videos for homework a lot of the time, and I'm getting in trouble with my teachers for it, even after explaining my situation at least twice. Not only can I not visit YouTube.com, I can't watch any videos on websites (like my school sites) that are linked from/saved from YouTube.
My dad and I are the most tech-savvy people in our family, and even we can't figure it out. Is it because YouTube hasn't updated to an SHA-2 server or what? I know that this can happen due to problems with an administrator account or a router, but everything with that is fine. It's not only happening to me though, my sister's and brothers Chromebooks are doing this, too.
The weird thing is though, if I connect to the WiFi at my school, YouTube works. We've tried restarting the router, but something is happening in between the internet connection and the server that YouTube runs on, or the actual site itself.
Thanks in advance! Sort it out Google. Removing the view certificate from the padlock in the 'omnibox' is rubbish. It makes it harder to check a sites security and authenticity. Having to go in to the Developre tools instead is logn winded and a pain.
Also changing the keyboard short-cut for back a page from the single key backspace key to a multi-key ALT and Left Arrow that can't be done with one hand (unless you have freakishly large hands or a wierd keyboard layout) These changes are making Chrome less user friendly. Please stop it Google, you're spoiling my favourite browser, and making work life more laborious. Roma Rogers 10/3/2017, 3:41 น. If it is not broken, why fix?
I have been trying to get into swagbucks since I installed this update and I can't get the page up normally. I know how to protect myself and I don't need the secure setting to keep trying to open it up.how do I get rid of the secure in my address bar? I don't want it, every time i click on swagbucks, it opens it with Swagbucks does not open with that.
Please tell me how to get rid of it permanently. I have what I need to stay protected. Jennysue19 11/3/2017, 4:10 น.
. Release date is the date of first release. All channels have subsequent updates which are not shown.
For release update history see. The first stable release in Windows, macOS and Linux was Google Chrome 5.0.375. The first stable release on Android was Chrome 18.0.1025123 (Chrome for Android).
Old development and beta builds are not shown after they become stable releases. As of Chrome 26, Linux installations of the browser may be updated only on systems that support GCC v4.6 and GTK v2.24 or later. Thus systems such as Ubuntu Lucid 10.04 LTS, Debian 6's 2.20, and RHEL 6's 2.18 are now among those marked as deprecated.
As of Chrome 59, Linux Chrome defaults to GTK+3. Older versions of Linux, e.g. RHEL 6 or CentOS 6, with only GTK+2 support, are not able to run this version of Chrome. Red Hat's GTK+2 build of Firefox ESR is probably the last remaining regularly updated browser on RHEL 6/CentOS 6. Versions 6–32 had counterparts, until its development was discontinued.
As of version 50, macOS 10.6, 10.7, 10.8, Windows XP and Vista are no longer supported. Standalone builds can be found on Google's. References. Retrieved May 16, 2015.
September 1, 2008. Retrieved July 11, 2012. Laforge, Anthony. Retrieved May 25, 2010.
March 17, 2010. Retrieved April 8, 2012. Rakowski, Brian (May 25, 2010). Retrieved May 25, 2010. June 30, 2010. Retrieved August 8, 2010. Rakowski, Brian (May 25, 2010).
Retrieved August 28, 2014. Chromium Blog. June 17, 2010. Retrieved October 24, 2010. Retrieved October 24, 2010. Retrieved December 3, 2010. Retrieved December 17, 2010.
Retrieved February 3, 2011. Retrieved January 21, 2011. Retrieved March 21, 2012. Retrieved December 17, 2010. March 8, 2011.
Retrieved April 8, 2012. March 22, 2011. Retrieved March 23, 2011. Rura, Steve (March 2011). Retrieved March 22, 2011.
June 7, 2011. Retrieved June 7, 2011. Google Operating System (Unofficial Google Blog). June 7, 2011. Retrieved February 4, 2012. Bentzel, Chris (June 16, 2011).
Retrieved August 21, 2011. Retrieved August 15, 2011. Langley, Adam (August 16, 2010).
Retrieved April 8, 2012. Retrieved August 15, 2011. Retrieved September 19, 2011. Retrieved September 23, 2011. July 30, 2010. Retrieved April 8, 2012. July 1, 2010.
Retrieved February 4, 2012. October 6, 2011. Retrieved February 4, 2012. ^. Retrieved February 9, 2012.
Archived from on February 6, 2012. Retrieved February 9, 2012. June 28, 2009. Retrieved April 8, 2012. Ilascu, Ionut (January 19, 2012).
Retrieved December 27, 2012. Retrieved May 23, 2012. April 10, 2012. Retrieved May 23, 2012. February 11, 2012.
Retrieved May 15, 2012. May 16, 2012. Retrieved May 16, 2012. Peter Beverloo. Retrieved May 23, 2012. May 29, 2012.
Retrieved June 1, 2011. August 21, 2012.
Retrieved August 22, 2012. September 2, 2008. Retrieved March 23, 2013. Bright, Peter (September 14, 2012). Ars Technica.
Retrieved November 2, 2012. Retrieved November 14, 2012. Retrieved November 9, 2012.
Retrieved March 23, 2013. Hewitt, Ed (February 21, 2013). Retrieved March 23, 2013. Chromium Blog.
December 24, 2012. Retrieved December 24, 2012. Chromium Blog. January 14, 2013. Retrieved January 19, 2013. Chromium Blog. January 18, 2013.
Retrieved January 19, 2013. February 5, 2013. Retrieved February 19, 2013. ^ Govindan, Dharani (March 26, 2013). Chrome Releases.
Retrieved March 26, 2013. May 21, 2013. Retrieved May 22, 2013. March 4, 2013. Retrieved March 30, 2013. Protalinski, Emil.
The Next Web. Retrieved April 5, 2013. Shankland, Stephen. Retrieved April 5, 2013.
Finley, Klint. Wired Enterprise. Retrieved April 5, 2013. Retrieved June 17, 2013. Protalinski, Emil. The Next Web.
Retrieved June 17, 2013. Retrieved July 11, 2013. Retrieved February 22, 2013.
October 15, 2013. Retrieved October 24, 2015. Chrome Story. September 13, 2013.
Chromium Blog. Chromium Blog. Chrome Releases.
Retrieved March 9, 2014. September 3, 2014. Retrieved September 3, 2014. August 26, 2014. Retrieved August 27, 2014. October 21, 2014.
Retrieved October 24, 2014. October 7, 2014. Retrieved October 7, 2014. October 8, 2014. Retrieved October 8, 2014. October 7, 2014.
Retrieved October 7, 2014. November 18, 2014.
Retrieved November 18, 2014. November 12, 2014. Retrieved November 12, 2014. October 14, 2014.
Retrieved November 14, 2014. January 21, 2015. Retrieved January 21, 2015.
January 21, 2015. Retrieved January 21, 2015. January 20, 2015. Retrieved January 20, 2015. March 3, 2015. Retrieved March 3, 2015.
March 11, 2015. Retrieved March 11, 2015. April 14, 2015. Retrieved April 14, 2015. April 15, 2015. Retrieved April 15, 2015.
May 19, 2015. Retrieved May 19, 2015. May 27, 2015.
Retrieved May 27, 2015. Brinkmann, Martin (March 3, 2015).
GHacks Technology News. Retrieved August 31, 2015. Tung, Liam (March 4, 2015). Retrieved August 31, 2015. July 21, 2015. Retrieved July 21, 2015.
July 29, 2015. Retrieved July 29, 2015. July 22, 2015. Retrieved July 22, 2015. September 1, 2015. Retrieved September 1, 2015.
September 1, 2015. Retrieved September 1, 2015. October 13, 2015. Retrieved October 13, 2015. October 14, 2015.
Retrieved October 15, 2015. December 1, 2015. Retrieved December 1, 2015.
December 2, 2015. Retrieved December 3, 2015. January 20, 2016. Retrieved January 20, 2016. March 2, 2016.
Retrieved March 2, 2016. March 9, 2016. Retrieved March 9, 2016. April 13, 2016. Retrieved April 13, 2016.
May 25, 2016. Retrieved May 25, 2016. June 7, 2016. Retrieved September 10, 2016. July 20, 2016.
Retrieved July 20, 2016. July 27, 2016. Retrieved July 28, 2016. August 31, 2016.
Retrieved August 31, 2016. September 7, 2016. Retrieved September 8, 2016. Google Developers.
Retrieved November 3, 2016. October 12, 2016. Retrieved October 12, 2016. October 19, 2016. Retrieved October 20, 2016. December 1, 2016. Retrieved December 2, 2016.
December 6, 2016. Retrieved December 7, 2016. January 25, 2017. Retrieved January 26, 2017. February 1, 2017. Retrieved February 2, 2017. March 9, 2017.
Retrieved March 9, 2017. February 2, 2017. March 16, 2017. Retrieved March 17, 2017. April 19, 2017.
Retrieved April 19, 2017. April 25, 2017. Retrieved April 26, 2017. June 5, 2017. Retrieved June 6, 2017. LePage, Pete (May 2017).
Google Developers. Retrieved June 10, 2017. June 6, 2017.
Retrieved June 7, 2017. July 25, 2017. Retrieved July 25, 2017. August 1, 2017. Retrieved August 2, 2017. September 5, 2017.
Retrieved September 5, 2017. September 5, 2017. Retrieved September 6, 2017.
October 17, 2017. Retrieved October 18, 2017.
Google Developers. Retrieved October 18, 2017. October 24, 2017.
Retrieved October 24, 2017. December 6, 2017. Retrieved December 6, 2017. Google Developers. Retrieved December 14, 2017. December 5, 2017.
Retrieved December 6, 2017. January 24, 2018. Retrieved January 24, 2018. Google Developers. Retrieved January 25, 2018.
January 23, 2018. Retrieved January 24, 2018.
March 6, 2018. Retrieved March 6, 2018. Google Developers. Retrieved March 6, 2018. March 6, 2018.
Retrieved March 6, 2018. April 17, 2018.
Retrieved April 18, 2018. Google Developers. Retrieved April 18, 2018. April 17, 2018. Retrieved April 18, 2018.
May 29, 2018. Retrieved May 29, 2018. Google Developers. Retrieved May 29, 2018. May 31, 2018.
Retrieved May 31, 2018. July 24, 2018. Retrieved July 24, 2018. Google Developers. Retrieved July 24, 2018. July 24, 2018. Retrieved July 25, 2018.
September 4, 2018. Retrieved September 4, 2018. Google Developers. Retrieved September 4, 2018. September 4, 2018. Retrieved September 4, 2018.
October 16, 2018. Retrieved October 16, 2018. Google Developers. Retrieved September 18, 2018. Google Developers.
Retrieved October 16, 2018. October 17, 2018. Retrieved October 17, 2018. Pichai, Sundar. Retrieved June 27, 2012. Retrieved February 9, 2012.
Retrieved February 9, 2012. February 14, 2013. Archived from on December 8, 2013. Retrieved March 30, 2013. Chromium Blog.
External links. for different versions of Chrome.