Comment #9 on issue 22760 by [email protected]: IE User Agent string contains 'chromeframe' string even when chromeframe add-on is disabled in IE http://code.google.com/p/chromium/issues/detail?id=22760
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=29370
------------------------------------------------------------------------
r29370 | [email protected] | 2009-10-16 21:48:37 -0700 (Fri, 16 Oct 2009)
| 2 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/bho.cc?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/chrome_frame.gyp?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/chrome_tab.cc?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/html_utils.cc?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/html_utils.h?r1=29370&r2=29369
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/http_negotiate.cc
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/http_negotiate.h
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/protocol_sink_wrap.cc?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/protocol_sink_wrap.h?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/test/html_util_unittests.cc?r1=29370&r2=29369
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/test/http_negotiate_unittest.cc
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/utils.h?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/vtable_patch_manager.cc?r1=29370&r2=29369
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome_frame/vtable_patch_manager.h?r1=29370&r2=29369
Add the chromeframe tag to the user agent header at runtime instead of
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
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
