summaryrefslogtreecommitdiffstats
path: root/chrome_frame/chrome_frame.gyp
Commit message (Collapse)AuthorAgeFilesLines
* GPU service now runs on new thread in browser process when --single-process ↵apatrick@chromium.org2011-01-131-0/+4
| | | | | | | | | | | is specified. TEST=try BUG=none Review URL: http://codereview.chromium.org/6189008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71359 0039d316-1c4b-4281-b951-d872f2087c98
* Integrate the Ready Mode prompt with IE and Chrome Frame. In Ready Mode, ↵erikwright@chromium.org2011-01-121-2/+4
| | | | | | | | | | prompts are displayed when the user browses to GCF-enabled sites, allowing the user to permanently activate, permanently decline, or temporarily decline Chrome Frame. BUG=None TEST=chrome_frame_unittests --gtest_filter=Ready* && chrome_frame_unittests --gtest_filter=Infobar* && setup.exe --chrome-frame --ready-mode --multi-install --system--level --chrome Review URL: http://codereview.chromium.org/6040003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71215 0039d316-1c4b-4281-b951-d872f2087c98
* Marking the following targets for non-incremental linking independentjoi@chromium.org2011-01-111-2/+2
| | | | | | | | | | | | | | | | | | | | | of 32/64 bits, as they have been causing out of memory errors even on 64-bit builders.: chrome_frame_tests chrome_frame_perftests chrome_dll_nacl_win64 browser_tests nacl_ui_tests nacl_sandbox_tests sync_integration_tests interactive_ui_tests BUG=none TEST=it builds Review URL: http://codereview.chromium.org/6113006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71077 0039d316-1c4b-4281-b951-d872f2087c98
* Remove unused ChromeFrameHTTPServer class.tfarina@chromium.org2011-01-111-5/+1
| | | | | | | | | BUG=None TEST=trybots Review URL: http://codereview.chromium.org/6214001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70983 0039d316-1c4b-4281-b951-d872f2087c98
* Create a new breakpad target that is built in a manner suitable for use in a ↵robertshield@chromium.org2011-01-101-1/+1
| | | | | | | | | | | DLL. Specifically, do NOT #define BREAKPAD_NO_TERMINATE_THREAD in this new target since that makes crash reporting shutdown racy and crash-prone. BUG=68536 TEST=NONE Review URL: http://codereview.chromium.org/6102001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70898 0039d316-1c4b-4281-b951-d872f2087c98
* Don't build using GPO for the tests EXEs we build duringnsylvain@chromium.org2010-12-271-0/+11
| | | | | | | | | our official build. BUG=none Review URL: http://codereview.chromium.org/6034011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70195 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 68944 - Revert "Add named testing interface."nirnimesh@chromium.org2010-12-231-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reverting the revert of named interface CL. Followup CL which addresses Pawel's comments is up at http://codereview.chromium.org/5967003/ http://src.chromium.org/viewvc/chrome?view=rev&revision=67300 The change has been approved conditionally, i.e. if the outstanding review comments are handled in a follow-up as the top priority. Two weeks have passed, and I have not seen the follow-up. It is risky to keep this change in the tree, as it is already non-trivial to revert. Conflicts: chrome/browser/automation/automation_provider.cc chrome/test/ui/named_interface_uitest.cc ipc/ipc_channel_posix.cc TBR=nirnimesh BUG=chromium-os:8512 TEST=none Review URL: http://codereview.chromium.org/5707006 TBR=phajdan.jr@chromium.org BUG=chromium-os:8512 TEST=ui_tests --gtest_filter=NamedInterfaceTest.FLAKY_BasicNamedInterface Review URL: http://codereview.chromium.org/6012006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70089 0039d316-1c4b-4281-b951-d872f2087c98
* Get rid of the dependency of a number of chrome frame projects on the ↵ananta@chromium.org2010-12-161-4/+7
| | | | | | | | | | | | | xulrunner_sdk target which brings in dependency on nspr needlessly. BUG=43461 TEST=it compiles Review URL: http://codereview.chromium.org/5931001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69372 0039d316-1c4b-4281-b951-d872f2087c98
* Attempt to get rid of chrome_frame_perftests dependency on nspr.lib which ↵ananta@chromium.org2010-12-151-1/+1
| | | | | | | | | | | | | | | causes random build errors. TBR=amit BUG=none TEST=none Review URL: http://codereview.chromium.org/5845002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69213 0039d316-1c4b-4281-b951-d872f2087c98
* Implement a ReadyPromptContent that displays a prompt to accept, temporarily ↵erikwright@chromium.org2010-12-141-2/+13
| | | | | | | | | | decline, or permanently decline ready mode. Implement a RegistryReadyModeState that manages the state (based on user's decision) in the registry. Interfaces to integrate those with the installer. BUG=None TEST=chrome_frame_unittests --gtest_filter='Ready*' Review URL: http://codereview.chromium.org/5747002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69175 0039d316-1c4b-4281-b951-d872f2087c98
* Fix ChromeFrame perf test builder redness by delay loading nspr4.dll. We ↵ananta@chromium.org2010-12-141-1/+5
| | | | | | | | | | | | | | need to investigate where this dependency comes from. TBR=amit TEST=none BUG=none Review URL: http://codereview.chromium.org/5757004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69103 0039d316-1c4b-4281-b951-d872f2087c98
* Add support for gcf:about:plugins in chrome frame full tab mode. The URL ↵ananta@chromium.org2010-12-141-0/+3
| | | | | | | | | | | | | | | | | | | validation code path in ChromeFrame now takes in an interface NavigationConstraints which allows the delegateslike the ActiveX, ActiveDocument and the NPAPI plugins to control the navigation decisions. We no longer refer to the InternetSecurityManager interface which is IE only for performing zone decisions in the ChromeFrame NPAPI plugin. Fixes bug http://code.google.com/p/chromium/issues/detail?id=66118 BUG=66118 TEST=Covered by additional CanNavigate unit tests. Review URL: http://codereview.chromium.org/5698005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69101 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Add named testing interface."phajdan.jr@chromium.org2010-12-111-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | http://src.chromium.org/viewvc/chrome?view=rev&revision=67300 The change has been approved conditionally, i.e. if the outstanding review comments are handled in a follow-up as the top priority. Two weeks have passed, and I have not seen the follow-up. It is risky to keep this change in the tree, as it is already non-trivial to revert. Conflicts: chrome/browser/automation/automation_provider.cc chrome/test/ui/named_interface_uitest.cc ipc/ipc_channel_posix.cc TBR=nirnimesh BUG=chromium-os:8512 TEST=none Review URL: http://codereview.chromium.org/5707006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68944 0039d316-1c4b-4281-b951-d872f2087c98
* Add support for detecting text selection in chrome frame tests. This ↵kkania@chromium.org2010-12-091-0/+3
| | | | | | | | | | requires adding support for IAccessible2 interfaces. BUG=none TEST=none Review URL: http://codereview.chromium.org/4406002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68680 0039d316-1c4b-4281-b951-d872f2087c98
* Create new test binary for Chrome Frame for running QA tests. Original patch ↵kkania@chromium.org2010-12-081-0/+74
| | | | | | | | | by mberkowitz@chromium.org. BUG=none TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68546 0039d316-1c4b-4281-b951-d872f2087c98
* Add an infobar facility to Chrome Frame. Allows clients to display and hide ↵erikwright@chromium.org2010-12-031-0/+11
| | | | | | | | | | arbitrary content at the top or botom of an IE tab. BUG=None TEST=chrome_frame_unittests --gtest_filter=Infobars* Review URL: http://codereview.chromium.org/4766003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68176 0039d316-1c4b-4281-b951-d872f2087c98
* Rename module_utils.cc|h and associated test to dll_redirector.cc|h etc. to ↵robertshield@chromium.org2010-12-031-3/+3
| | | | | | | | | | | match what's actually in those files. It's been a TODO for a while and a recent chat shamed me into action. BUG=NONE TEST=NONE Review URL: http://codereview.chromium.org/5560002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68128 0039d316-1c4b-4281-b951-d872f2087c98
* Always use persistent profile for CF+CEEE installs.joi@chromium.org2010-12-011-0/+2
| | | | | | | | | BUG=64840 TEST=With --enable-ceee, CF profiles on IE7 should not be under Temporary Internet Files. Review URL: http://codereview.chromium.org/5254012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67890 0039d316-1c4b-4281-b951-d872f2087c98
* Undo removal of chrome_dll_version from r67457.joi@chromium.org2010-11-301-2/+2
| | | | | | | | | | | | | This is not a straight revert as we keep the part where chrome.dll directly includes the generated .rc file instead of having it included via chrome_dll.rc, as that seems to cause other dependency issues. BUG=none TEST=it builds, incremental builds on changes to chrome/VERSION work. Review URL: http://codereview.chromium.org/5259007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67657 0039d316-1c4b-4281-b951-d872f2087c98
* Use BRANDING settings for IE CEEE. Simplify chrome_dll_version handling.joi@chromium.org2010-11-261-1/+1
| | | | | | | | | | | | | | | | | | | Adding new CEEE_PRODUCT_FULLNAME key to the BRANDING file. Adapting version.h.in to define a preprocessor constant for it. Using this and the other version/product name constants in IE CEEE's .rc files. Piggybacking on MAD's recent changes to make %NAME% a variable in the .rgs files to fairly easily get the product name from branding in there. Naming the toolband with the product name directly (as it is what shows up in IE's View/Toolbars menu), the BHO with an added "Helper" and the broker with an added "Broker". Removing the 'chrome_dll_version' target from chrome.gyp, and skipping code generation of chrome_dll_version.rc. Instead we have a source file with that name, that includes the verson.h generated by the 'chrome_version_header' target. This is cleaner and less code generation. Fixing 'chrome_dll_nacl64' target, it seemed like it wanted to have version information, but it didn't. Cleaning up the way sources are specified in several of the chrome_tests.gypi targets, to use fewer source! statements just to remove source files that are Windows-only (put them in the Windows-only section instead). BUG=none TEST=Visible change should be that user-visible names in Chromium builds are like "Chromium Extensions Execution Environment" (with "Broker" or "Helper" appended when appropriate), i.e. they lose the "Google" part. Review URL: http://codereview.chromium.org/5360002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67457 0039d316-1c4b-4281-b951-d872f2087c98
* Add named testing interface. This allows you to connect to a pre-existing ↵nirnimesh@chromium.org2010-11-241-1/+5
| | | | | | | | | | | | | | | | | | | | | Chrome process and run tests on it. This is an addition to the low level interface underlying testing frameworks like PyAuto and WebDriver. Normally, test frameworks communicate with Chrome over an unnamed socket pair on POSIX. The test creates the socket pair and then launches the browser as a child process, passing an open file descriptor for one end of the socket to the browser. This change adds a command line switch that, when passed to the browser, causes it to listen on a named socket instead, eliminating this parent/child process requirement. Therefore, you can potentially connect any number of tests to a preexisting browser process. For ChromeOS, this allows you to run tests on the instance of Chrome that is launched on startup, which controls things like the login and lock screens, the battery meter, the wireless UI, etc. Currently there is no way to run tests on a pre-existing Chrome instance. Eventually this will also allow you to connect both PyAuto and WebDriver to the same Chrome instance and run both in the same test. If you pass the browser the following command line switch: ./chrome --testing-channel=NamedTestingInterface:/path/to/file This causes the browser to listen for incoming connections. An AutomationProxy can connect to the browser by connecting a Unix domain socket to the specified path and control the browser over the socket. This is currently only for POSIX. Windows support will come in a future change. Also, this initial change only allows one connection; multiple connection support will come in a future change. BUG=chromium-os:8512 TEST=Run Chrome with --testing-interface=/var/tmp/NamedTestingInterface, then run NamedInterfaceTest.BasicNamedInterface under ui_tests. Review URL: http://codereview.chromium.org/4202004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67300 0039d316-1c4b-4281-b951-d872f2087c98
* Reconstructing 67000.bradnelson@google.com2010-11-231-1/+1
| | | | | | | | | | | | | | (python24 -> python26). Regression in nacl fixed, new DEPS change. BUG=None TEST=NOne Review URL: http://codereview.chromium.org/5310001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67057 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting 67000.bradnelson@google.com2010-11-221-1/+1
| | | | | | | | | | BUG=None TEST=None TBR=nsylvain Review URL: http://codereview.chromium.org/5272001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67004 0039d316-1c4b-4281-b951-d872f2087c98
* Switching chrome to use python26 in place of python24.bradnelson@google.com2010-11-221-1/+1
| | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/5121009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67000 0039d316-1c4b-4281-b951-d872f2087c98
* Always use flag needed by CEEE. Now that we use the same profile forjoi@chromium.org2010-11-211-4/+7
| | | | | | | | | | | | | | | | CF and CEEE, we need to ensure they both start Chrome with the same flags. Since IChromeFramePrivileged is a private/unfrozen interface, I simply removed the GetChromeExtraArguments method as we are no longer using it. BUG=63427 TEST=none Review URL: http://codereview.chromium.org/5109006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66916 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 66840 - Add named testing interface. This allows you to connect to a ↵kkania@chromium.org2010-11-201-6/+3
| | | | | | | | | | | | | | | | | | | | | | | | pre-existing Chrome process and run tests on it. This is an addition to the low level interface underlying testing frameworks like PyAuto and WebDriver. Normally, test frameworks communicate with Chrome over an unnamed socket pair on POSIX. The test creates the socket pair and then launches the browser as a child process, passing an open file descriptor for one end of the socket to the browser. This change adds a command line switch that, when passed to the browser, causes it to listen on a named socket instead, eliminating this parent/child process requirement. Therefore, you can potentially connect any number of tests to a preexisting browser process. For ChromeOS, this allows you to run tests on the instance of Chrome that is launched on startup, which controls things like the login and lock screens, the battery meter, the wireless UI, etc. Currently there is no way to run tests on a pre-existing Chrome instance. Eventually this will also allow you to connect both PyAuto and WebDriver to the same Chrome instance and run both in the same test. If you pass the browser the following command line switch: ./chrome --testing-channel=NamedTestingInterface:/path/to/file This causes the browser to listen for incoming connections. An AutomationProxy can connect to the browser by connecting a Unix domain socket to the specified path and control the browser over the socket. This is currently only for POSIX. Windows support will come in a future change. Also, this initial change only allows one connection; multiple connection support will come in a future change. BUG=chromium-os:8512 TEST=Run Chrome with --testing-interface=/var/tmp/NamedTestingInterface, then run NamedInterfaceTest.BasicNamedInterface under ui_tests. Review URL: http://codereview.chromium.org/4202004 TBR=nirnimesh@chromium.org Review URL: http://codereview.chromium.org/5177007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66856 0039d316-1c4b-4281-b951-d872f2087c98
* Add named testing interface. This allows you to connect to a pre-existing ↵nirnimesh@chromium.org2010-11-191-3/+6
| | | | | | | | | | | | | | | | | | | | | Chrome process and run tests on it. This is an addition to the low level interface underlying testing frameworks like PyAuto and WebDriver. Normally, test frameworks communicate with Chrome over an unnamed socket pair on POSIX. The test creates the socket pair and then launches the browser as a child process, passing an open file descriptor for one end of the socket to the browser. This change adds a command line switch that, when passed to the browser, causes it to listen on a named socket instead, eliminating this parent/child process requirement. Therefore, you can potentially connect any number of tests to a preexisting browser process. For ChromeOS, this allows you to run tests on the instance of Chrome that is launched on startup, which controls things like the login and lock screens, the battery meter, the wireless UI, etc. Currently there is no way to run tests on a pre-existing Chrome instance. Eventually this will also allow you to connect both PyAuto and WebDriver to the same Chrome instance and run both in the same test. If you pass the browser the following command line switch: ./chrome --testing-channel=NamedTestingInterface:/path/to/file This causes the browser to listen for incoming connections. An AutomationProxy can connect to the browser by connecting a Unix domain socket to the specified path and control the browser over the socket. This is currently only for POSIX. Windows support will come in a future change. Also, this initial change only allows one connection; multiple connection support will come in a future change. BUG=chromium-os:8512 TEST=Run Chrome with --testing-interface=/var/tmp/NamedTestingInterface, then run NamedInterfaceTest.BasicNamedInterface under ui_tests. Review URL: http://codereview.chromium.org/4202004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66840 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 66350 - Add named testing interface. This allows you to connect to a ↵nirnimesh@chromium.org2010-11-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | pre-existing Chrome process and run tests on it. This is an addition to the low level interface underlying testing frameworks like PyAuto and WebDriver. Normally, test frameworks communicate with Chrome over an unnamed socket pair on POSIX. The test creates the socket pair and then launches the browser as a child process, passing an open file descriptor for one end of the socket to the browser. This change adds a command line switch that, when passed to the browser, causes it to listen on a named socket instead, eliminating this parent/child process requirement. Therefore, you can potentially connect any number of tests to a preexisting browser process. For ChromeOS, this allows you to run tests on the instance of Chrome that is launched on startup, which controls things like the login and lock screens, the battery meter, the wireless UI, etc. Currently there is no way to run tests on a pre-existing Chrome instance. Eventually this will also allow you to connect both PyAuto and WebDriver to the same Chrome instance and run both in the same test. If you pass the browser the following command line switch: ./chrome --testing-channel=NamedTestingInterface:/path/to/file This causes the browser to listen for incoming connections. An AutomationProxy can connect to the browser by connecting a Unix domain socket to the specified path and control the browser over the socket. This is currently only for POSIX. Windows support will come in a future change. Also, this initial change only allows one connection; multiple connection support will come in a future change. BUG=chromium-os:8512 TEST=Run Chrome with --testing-interface=/var/tmp/NamedTestingInterface, then run NamedInterfaceTest.BasicNamedInterface under ui_tests. Review URL: http://codereview.chromium.org/4202004 TBR=nirnimesh@chromium.org Review URL: http://codereview.chromium.org/5139001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66368 0039d316-1c4b-4281-b951-d872f2087c98
* Add named testing interface. This allows you to connect to a pre-existing ↵nirnimesh@chromium.org2010-11-171-0/+1
| | | | | | | | | | | | | | | | | | | | | Chrome process and run tests on it. This is an addition to the low level interface underlying testing frameworks like PyAuto and WebDriver. Normally, test frameworks communicate with Chrome over an unnamed socket pair on POSIX. The test creates the socket pair and then launches the browser as a child process, passing an open file descriptor for one end of the socket to the browser. This change adds a command line switch that, when passed to the browser, causes it to listen on a named socket instead, eliminating this parent/child process requirement. Therefore, you can potentially connect any number of tests to a preexisting browser process. For ChromeOS, this allows you to run tests on the instance of Chrome that is launched on startup, which controls things like the login and lock screens, the battery meter, the wireless UI, etc. Currently there is no way to run tests on a pre-existing Chrome instance. Eventually this will also allow you to connect both PyAuto and WebDriver to the same Chrome instance and run both in the same test. If you pass the browser the following command line switch: ./chrome --testing-channel=NamedTestingInterface:/path/to/file This causes the browser to listen for incoming connections. An AutomationProxy can connect to the browser by connecting a Unix domain socket to the specified path and control the browser over the socket. This is currently only for POSIX. Windows support will come in a future change. Also, this initial change only allows one connection; multiple connection support will come in a future change. BUG=chromium-os:8512 TEST=Run Chrome with --testing-interface=/var/tmp/NamedTestingInterface, then run NamedInterfaceTest.BasicNamedInterface under ui_tests. Review URL: http://codereview.chromium.org/4202004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66350 0039d316-1c4b-4281-b951-d872f2087c98
* Adding a privileged callback used in IE CF to check whether to showjoi@chromium.org2010-11-101-35/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | the version mismatch warning dialog. Used this in ceee/ to only show it once per tab. Changed the logic in Firefox to show the warning dialog even when in privileged mode. This will mean it gets shown once per Firefox window. Wrote a unit test for the additional logic in ChromeFrameActivex. To write the unit test, used com_mock.py to generate a mock of the IChromeFramePrivileged interface. This can be extended to generate mocks of the other CF interfaces. Discovered duplication of np_browser_functions.h and .cc, resolved this to a single copy (the one under chrome_frame). Changed things around so chrome_tab.idl is built only once; this also lets me more easily depend on it in the com_mock rule. BUG=none TEST=chrome_frame_unittests.exe Review URL: http://codereview.chromium.org/4563001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65613 0039d316-1c4b-4281-b951-d872f2087c98
* Implementation of single-module-per-logon-session-per-profile implementation ↵robertshield@chromium.org2010-11-051-0/+1
| | | | | | | | | | | | for Chrome Frame. BUG=61383 TEST=Run IE with version X of CF loaded. Register version Y of CF. Run a second IE process, notice that version Y when loaded defers to version X. Review URL: http://codereview.chromium.org/4144008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65236 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up some dependencies in Chrome Framesiggi@chromium.org2010-11-041-39/+11
| | | | | | | | | | | | | | | | | Libraries that depend on other targets cause the propagation of the other targets closure of library targets to all their dependents. This was the case with chrome_frame_ie, which caused npchrome_frame to link gmock and gtest. Best case, this will slow down the build. Worst case we're open to regressions that ship test code, as useful as our unittests are, I don't think users have much appreciation for installing them :). This may require another change in build\all.gyp, as building the crash tests is no longer implicit in building npchrome_frame. Also removed the base_noicu target, as all its dependents have a dependency on base.lib, so this won't prevent ICU usage regressions. TEST=none BUG=none Review URL: http://codereview.chromium.org/4406001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65043 0039d316-1c4b-4281-b951-d872f2087c98
* Add explicit build dependencies from npchrome_frame to chrome and ↵robertshield@chromium.org2010-11-021-0/+2
| | | | | | | | | | | chrome_dll. This is to avoid having non-versioned matched components in the build directory if only buildingg npchrome_frame which causes all manner of trouble. BUG=version-mismatched binaries can reside in the build folder when building only npchrome_frame TEST=NONE Review URL: http://codereview.chromium.org/4288001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64759 0039d316-1c4b-4281-b951-d872f2087c98
* Move debug-related stuff from base to the base/debug directory and use thebrettw@chromium.org2010-10-261-0/+1
| | | | | | | | | | | | | | | | base::debug namespace. This splits apart debug_util into base/debugger and base/stack_trace There are still two functions in debug_util that I'm not sure what to do with. Since this uses the base::debug namespace, I removed the functions in debugger.h from the static class and just made them free functions in the namespace. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/3945002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63859 0039d316-1c4b-4281-b951-d872f2087c98
* Enable developers to conditionally activate Chrome Frame, depending on the ↵erikwright@chromium.org2010-10-251-0/+1
| | | | | | | | | | version of the host IE browser. BUG=52601 TEST=[chrome_frame_unittests / UtilTests.XUaCompatibleDirectiveTest], [chrome_frame_tests / HeaderTest.*] Review URL: http://codereview.chromium.org/3978001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63728 0039d316-1c4b-4281-b951-d872f2087c98
* Revert of a revert of a patch that re-enabled automation protocol version ↵robertshield@chromium.org2010-10-211-0/+2
| | | | | | | | | | | | | | mismatch checking in CF. Original revision: r63211 Revert revision: r63239 Previously, our version information wasn't getting updated properly through incremental builds which made the test builders unhappy. That was fixed in r63355. This should now be safe to commit. Review URL: http://codereview.chromium.org/4034004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63364 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting this as this causes a message box to show up on the builders ↵ananta@chromium.org2010-10-201-2/+0
| | | | | | | | | | | | | | | | | | | | | indicating that the chrome and chrome frame versions are different which they are. Perhaps the version resource in chrome frame is just wrong and needs a clobber. Robert please investigate and reland Revert 63211 - Re-add the version mismatch checking which was removed at some point. Also add version information to chrome_frame_tests.exe. This will be needed for subsequent tests. Review URL: http://codereview.chromium.org/3879001 TBR=robertshield@chromium.org Review URL: http://codereview.chromium.org/3939002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63239 0039d316-1c4b-4281-b951-d872f2087c98
* Re-add the version mismatch checking which was removed at some point. Also ↵robertshield@chromium.org2010-10-201-0/+2
| | | | | | | | add version information to chrome_frame_tests.exe. This will be needed for subsequent tests. Review URL: http://codereview.chromium.org/3879001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63211 0039d316-1c4b-4281-b951-d872f2087c98
* Review URL: http://codereview.chromium.org/3685006stoyan@chromium.org2010-10-131-0/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62407 0039d316-1c4b-4281-b951-d872f2087c98
* Reland http://codereview.chromium.org/3528004/stoyan@chromium.org2010-10-061-0/+10
| | | | | | | | Initial skeleton for refactored ChromeFrameAutomationClient and AutomationProxy for the needs of ChromeFrame. TBR=amit Review URL: http://codereview.chromium.org/3567019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61665 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 61583 - Initial skeleton for refactored ChromeFrameAutomationClient ↵stoyan@chromium.org2010-10-061-10/+0
| | | | | | | | | | | | | and AutomationProxy for the needs of ChromeFrame. CFProxy is ready to some extent, while CFAC is mostly structure-only. Review URL: http://codereview.chromium.org/3528004 TBR=stoyan@chromium.org Review URL: http://codereview.chromium.org/3547013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61590 0039d316-1c4b-4281-b951-d872f2087c98
* Initial skeleton for refactored ChromeFrameAutomationClient and ↵stoyan@chromium.org2010-10-051-0/+10
| | | | | | | | | | AutomationProxy for the needs of ChromeFrame. CFProxy is ready to some extent, while CFAC is mostly structure-only. Review URL: http://codereview.chromium.org/3528004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61583 0039d316-1c4b-4281-b951-d872f2087c98
* This changelist consists of a test for the Delete Browsing History feature.erikwright@chromium.org2010-09-281-2/+21
| | | | | | | | | | | | | | | | | The feature was never covered by automated tests, and a recent changelist addressed a bug in the feature (http://codereview.chromium.org/3167040). The test validates the following: 1) That cached files are re-retrieved after the user requests their deletion. 2) That saved form data is deleted after the user requests its deletion. 3) That Chrome Frame tabs do not crash when the user deletes browsing history. BUG=56212 TEST= (1) Run "chrome_frame_tests.exe --gclient_filter=DeleteBro*" (should pass) (2) Run the test, and immediately lock your workstation before it starts. It should still pass. (3) Comment out the call to RemoveBrowsingData in DeleteChromeHistory::OnAutomationServerReady (chrome_frame/delete_chrome_history.cc) and run the test. It fails. (4) Revert changes from 3, comment out the check for low integrity level in DeleteChromeHistory::DeleteBrowsingHistory (same file) and run the test. It fails. Review URL: http://codereview.chromium.org/3365010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60779 0039d316-1c4b-4281-b951-d872f2087c98
* Correct problem with localized resource loading in Chrome Frame: we were not ↵robertshield@chromium.org2010-09-241-1/+3
| | | | | | | | | | | loading language DLLs that did not have a region specifier. BUG=56432 TEST=Chrome Frame loads correctly in non-region specific languages, e.g. French. Review URL: http://codereview.chromium.org/3439020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60465 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 60084 - A test for Chrome Frame delete browser history behaviour in IE8.erikwright@chromium.org2010-09-211-22/+3
| | | | | | | | | | | BUG=52612 TEST=chrome_frame_tests --gtest_filter=DeleteBrowsingHistoryTest.* Review URL: http://codereview.chromium.org/3365010/show TBR=erikwright@chromium.org Review URL: http://codereview.chromium.org/3487002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60100 0039d316-1c4b-4281-b951-d872f2087c98
* A test for Chrome Frame delete browser history behaviour in IE8.erikwright@chromium.org2010-09-211-3/+22
| | | | | | | | BUG=52612 TEST=chrome_frame_tests --gtest_filter=DeleteBrowsingHistoryTest.* Review URL: http://codereview.chromium.org/3365010/show git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60084 0039d316-1c4b-4281-b951-d872f2087c98
* Basic policy implementation for Chrome Frame. We read the policy settings ↵tommi@chromium.org2010-09-151-0/+3
| | | | | | | | | | | | | on first request and cache them. In order to refresh the policy settings the browser has to be restarted. Future implementations may support pushing out policy changes without requiring the user to restart the browser. TEST=Use the policy templates to change the default renderer ("Configure the default renderer for Chrome Frame") and relevant exclusion lists. BUG=29349 Review URL: http://codereview.chromium.org/3435004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59496 0039d316-1c4b-4281-b951-d872f2087c98
* FBTF: Move ctors/dtors into cc files.erg@google.com2010-09-131-0/+1
| | | | | | | | | | | | | This cleanup patch isn't as impactful; this only shrinks our .a files by 304k. This patch also renames chrome/browser/history/download_type.h to download_create_info.h because there are then two download_type.cc files and MSVS will have the .obj from one of those overwrite the other. BUG=none TEST=compiles Review URL: http://codereview.chromium.org/3351005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59264 0039d316-1c4b-4281-b951-d872f2087c98
* Adds a dependency on chrome.gyp:crash_service from ↵slightlyoff@chromium.org2010-09-071-0/+3
| | | | | | | | | | | chrome_frame.gyp:chrome_frame_tests since the tests refuse to start without the crash service built. TEST=clobber, build chrome_frame_tests, see if they run BUG=None Review URL: http://codereview.chromium.org/3295004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58765 0039d316-1c4b-4281-b951-d872f2087c98
* Disable incremental linking for chrome_frame_reliability_tests on 32 bits ↵maruel@chromium.org2010-09-031-1/+10
| | | | | | | | | | | | | | windows. It's that large. TBR=nsylvain BUG=none TEST=none Review URL: http://codereview.chromium.org/3296005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58532 0039d316-1c4b-4281-b951-d872f2087c98