chromium_src.git - central chromium sources

	Commit message (Collapse)	Author	Age	Files	Lines
*	Only switch to cf for text/html. With opt-in URLs we could mark a URL to be ↵	tommi@chromium.org	2010-04-21	1	-0/+11
\| \| \| \| \| \| \| \| \| \| \|	loaded in CF regardless of the target mime type. If CF turns around and wants to download the target, we would hit an infinite loop. TEST=Verify that issue 40046 is resolved. OptIn urls should work with the moniker patch and downloads should not cause an infinite loop. BUG=40046 Review URL: http://codereview.chromium.org/1715004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45226 0039d316-1c4b-4281-b951-d872f2087c98
*	Adding support for Chrome Frame to be loaded via the presence of an ↵	robertshield@chromium.org	2009-12-03	1	-1/+26
\| \| \| \| \| \| \| \| \| \| \| \| \|	X-UA-Compatible HTTP header (in addition to the meta tag support). Also pins the CF module into the process such that it won't get unloaded. Doing this to work around how we can get unloaded without unpatching properly. BUG=22802 TEST=Navigate to a web site whose server sends the X-UA-Compatible: chrome=1 HTTP header and ensure that the page is loaded in CF. Review URL: http://codereview.chromium.org/465009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33629 0039d316-1c4b-4281-b951-d872f2087c98
*	Add the chromeframe tag to the user agent header at runtime instead of ↵	tommi@chromium.org	2009-10-17	1	-0/+47
	statically in the registry.TEST=Try disabling GCF and see if the chromeframe tag in the user agent is still set. It should not be. Also make sure you don't have an older version installed... the chromeframe tag should not be in the registry - if it is, you've got an older version still registered. This should fix the issue with going to wave.google.com after disabling chrome frame and seeing the white page of death.R=amitBUG=22760 Review URL: http://codereview.chromium.org/259025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29370 0039d316-1c4b-4281-b951-d872f2087c98