diff options
| author | tommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-11 19:31:56 +0000 |
|---|---|---|
| committer | tommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-11 19:31:56 +0000 |
| commit | b22ef28f215f7475f1c0401f89e353a8aacf8def (patch) | |
| tree | 045041d0534fb9aa8b6b009e3a7499809b42e7ed /chrome/app/framework.order | |
| parent | 2f7aff273b0a1357e79d99e2f31ede1f702d8783 (diff) | |
| download | chromium_src-b22ef28f215f7475f1c0401f89e353a8aacf8def.zip chromium_src-b22ef28f215f7475f1c0401f89e353a8aacf8def.tar.gz chromium_src-b22ef28f215f7475f1c0401f89e353a8aacf8def.tar.bz2 | |
Use the OnHttpEquiv notification to switch to CF when the http-equiv meta tag is detected. This implementation is still behind the registry switch (set PatchProtocols to 0 in the registry). I will switch over to it wholesale in a separate patch.
We use the same mechanism for re-initiating the navigation we use to transfer downloads over to the host, so I moved the common code to utils.cc and added NavigateBrowserToMoniker.
When we see a browser instance attempting to load a CF document, we raise a TLS flag that we catch in HttpNegotiatePatch::ReportProgress when the mime type is being reported. This is the same place where we examine http headers and report the mime type.
BUG=n/a
TEST=Set PatchProtocols (REG_DWORD) to 0 in the CF HKCU config key and make sure we detect and handle the meta tag as well or better than before.
Review URL: http://codereview.chromium.org/489004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34366 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/app/framework.order')
0 files changed, 0 insertions, 0 deletions