Chromium Blog: chromeframe

84 captures

11 Apr 2015 - 10 Apr 2026

Sep	OCT	Nov
	21
2017	2018	2019

success

fail

About this capture

COLLECTED BY

Organization: Internet Archive

These crawls are part of an effort to archive pages as they are created and archive the pages that they refer to. That way, as the pages that are referenced are changed or taken from the web, a link to the version that was live when the page was written will be preserved.

Then the Internet Archive hopes that references to these archived pages will be put in place of a link that would be otherwise be broken, or a companion link to allow people to see what was originally intended by a page's authors.

The goal is to fix all broken links on the web. Crawls of supported "No More 404" sites.

Collection: GDELT

A daily crawl of more than 200,000 home pages of news sites, including the pages linked from those home pages. Site list provided by The GDELT Project

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20181021050436/https://blog.chromium.org/search/label/chromeframe

Chromium Blog

News and developments from the open source browser project

Non-Admin Chrome Frame Reaches Stable Channel

Tuesday, August 30, 2011

introducedheredownload pageGoogle groupissue trackerPosted by Greg Thompson, Software Engineer

Google

Labels: chromeframe

Introducing Non-Admin Chrome Frame

Monday, June 20, 2011

releasedannouncedhereChrome Frame FAQdiscussion groupissue trackerPosted by Robert Shield, Software Engineer

Google

Labels: chromeframe

Google Chrome Frame Developer Updates

Tuesday, February 9, 2010

Since Google Chrome Frame was released in September we've published regular updates to improve stability and integration with Internet Explorer. Today's update continues this work but also contains two key changes that developers should be aware of.
First, until now Google Chrome Frame has used the <meta> tag for invocation.

<meta equiv="X-UA-Compatible" content="chrome=1">

Unfortunately, doing this had a few potential problems, including some challenges for sites which couldn't place the <meta> tag early enough to trigger Google Chrome Frame reliably.
As of today, Google Chrome Frame additionally allows sites to serve an HTTP header for invocation. Use of the <meta> tag is still supported, but sites can take advantage of the new trigger by specifying an equivalent HTTP header:

X-UA-Compatible: chrome=1

This has the following benefits:

Sites that detect Google Chrome Frame can serve content with standard MIME types (including application/xhtml+xml), which Microsoft Internet Explorer does not natively support.
The HTTP header will always be detected, no matter how many other headers are served.
The HTTP header passes the W3C validator (which the <meta> tag syntax did not).
HTTP headers can be centrally configured in your web sever for blanket rollout of Google Chrome Frame support. For example, to enable GCF site-wide for browsers that support it, in Apache (with mod_headers and mod_setenvif enabled) specify a header directive like:

BrowserMatch chromeframe gcf

Header append X-UA-Compatible "chrome=1" env=gcf

</IfModule>

Secondly, today's release also renames the "cf:" protocol to "gcf:" and disables "gcf:" by default. You can enable it on your local system for testing by adding a REG_DWORD value named EnableGCFProtocol with a value of 1 to the following registry key: HKCU\Software\Google\ChromeFrame.
This change will help avoid misuse of this development-mode feature and will reduce the number of spurious compatibility issues reported.
Your copy of Google Chrome Frame should be automatically upgraded with these changes. To learn more, ask questions, or get involved, visit our site or join the Google Chrome Frame discussion group.
Posted by Alex Russell, Software Engineer