summaryrefslogtreecommitdiffstats
path: root/chrome_frame
Commit message (Collapse)AuthorAgeFilesLines
* Refactor the installer to support multi-install.tommi@chromium.org2010-12-011-16/+18
| | | | | | | | | | | | | | | | | | The installer now does its work based on distributions and target installation paths. Each distribution has exactly one target installation path but each installation path can have more than one distribution. In the absense of the --multi-install switch, the installer should continue to work as before. The biggest difference here is that we don't rely on a single global distribution object that controls the entire installation flow and we have a few classes for the new abstractions instead of global functions. It's far from perfect, but it's a step towards separating the core file package required for all distributions from the distributions themselves. Additionally, there are tons of little changes here such as consistant usage of FilePath and CommandLine instead of mixing them with std::wstring. TEST=Install, uninstall, upgrade, etc. Everything install related. BUG=61609 Review URL: http://codereview.chromium.org/5172011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67818 0039d316-1c4b-4281-b951-d872f2087c98
* The View->Source menu item in the IE9 menu bar is disabled for ChromeFrame ↵ananta@chromium.org2010-12-011-1/+1
| | | | | | | | | | | | | | | pages. This CL fixes that. We need to enable the MSHTML command id IDM_VIEWSOURCE Fixes bug http://code.google.com/p/chromium/issues/detail?id=64857 BUG=64857 TEST=Launch IE9 and observe that the View->Source menu item is enabled on chrome frame pages. Review URL: http://codereview.chromium.org/5367011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67806 0039d316-1c4b-4281-b951-d872f2087c98
* Post the WM_SYSKEYDOWN/WM_SYSKEYUP messages to the parent window when ↵ananta@chromium.org2010-11-301-9/+11
| | | | | | | | | | | | | | | | | | | ChromeFrame is active. This ensures that the Alt key is processed correctly in IE9, i.e. the menu bar is dropped down. On IE8 it appears that the Alt key is processed by the Ole control site in the context of WM_SYSKEYUP message even though it still returns S_FALSE. IE8 continues to work with this change as well. Fixes bug http://code.google.com/p/chromium/issues/detail?id=55763 BUG=55763 TEST=Launch IE9 and navigate to a chrome frame site. Press the Alt key and verify that the menu bar is dropped down. Review URL: http://codereview.chromium.org/5390004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67780 0039d316-1c4b-4281-b951-d872f2087c98
* Tweak chrome Frame Selenium test expectationsamit@chromium.org2010-11-301-3/+3
| | | | | | | | | | | | ...due to failures caused by popup blocker. TEST=FullTabSeleniumTest.Core BUG=NONE Review URL: http://codereview.chromium.org/5314011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67774 0039d316-1c4b-4281-b951-d872f2087c98
* net: Remove typedef net::URLRequest URLRequest;tfarina@chromium.org2010-11-302-7/+7
| | | | | | | | | BUG=64263 TEST=compiled locally, trybots Review URL: http://codereview.chromium.org/5384002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67762 0039d316-1c4b-4281-b951-d872f2087c98
* Disable CFOpenLinkInNewWindow on IE7.kkania@chromium.org2010-11-301-0/+5
| | | | | | | | BUG=64794 TEST=none Review URL: http://codereview.chromium.org/5315011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67737 0039d316-1c4b-4281-b951-d872f2087c98
* Add chrome frame context menu tests. Patch by mdu@chromium.org.kkania@chromium.org2010-11-306-1/+310
| | | | | | | | BUG=none TEST=none Review at http://codereview.chromium.org/3656002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67717 0039d316-1c4b-4281-b951-d872f2087c98
* Enable Selenium test for chrome Frameamit@chromium.org2010-11-301-1/+1
| | | | | | | | | | | as now we have selenium checkout on bots and it should work BUG=50372 TEST=FullTabSeleniumTest.Core Review URL: http://codereview.chromium.org/5380005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67714 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 67662 - FBTF: Remove unneeded headers from base/ (part 10)thestig@chromium.org2010-11-305-3/+9
| | | | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/5139006 TBR=thestig@chromium.org Review URL: http://codereview.chromium.org/5270010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67674 0039d316-1c4b-4281-b951-d872f2087c98
* FBTF: Remove unneeded headers from base/ (part 10)thestig@chromium.org2010-11-305-9/+3
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/5139006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67662 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
* Fix ChromeFrame perf builder redness caused by an event name change.ananta@chromium.org2010-11-301-1/+1
| | | | | | | | | | TBR=amit BUG=NONE TEST=Covered by existing chrome frame perf tests. Review URL: http://codereview.chromium.org/5361008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67632 0039d316-1c4b-4281-b951-d872f2087c98
* Attempt to fix the flakiness on IE9 in the ChromeFrame CtrlR test which ↵ananta@chromium.org2010-11-301-7/+7
| | | | | | | | | | | | tests page refresh. TBR=amit BUG=none TEST=Covered by existing ChromeFrame CtrlR test Review URL: http://codereview.chromium.org/5354005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67617 0039d316-1c4b-4281-b951-d872f2087c98
* net: Add namespace net to URLRequest and URLRequestJob classes.tfarina@chromium.org2010-11-281-3/+6
| | | | | | | | | BUG=64263 TEST=compiled locally and trybots Review URL: http://codereview.chromium.org/5298008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67497 0039d316-1c4b-4281-b951-d872f2087c98
* Fix NPAPI registrationgrt@chromium.org2010-11-271-2/+2
| | | | | | | | | BUG=none TEST=Set the persist NPAPI marker, upgrade GCF, then check to see if registration took place. Review URL: http://codereview.chromium.org/5366003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67482 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
* Implement exponential back-off mechanism.joi@chromium.org2010-11-251-1/+0
| | | | | | | | | | | | | | | | | | | | | | | Contributed by yzshen@google.com, original review http://codereview.chromium.org/4194001/ Implement exponential back-off mechanism. Enforce it at the URLRequestHttpJob level for all outgoing HTTP requests. The reason why to make this change is that we need back-off logic at a lower enough level to manage all outgoing HTTP traffic, so that the browser won't cause any DDoS attack. This change: 1) patches http://codereview.chromium.org/2487001/show, which is the exponential back-off implementation. 2) resolves conflicts with URLFetcher, by removing its own back-off logic: -- removes url_fetcher_protect.{h,cc}; -- integrates the sliding window mechanism of URLFetcherProtectEntry into RequestThrottlerEntry. 3) resolves conflicts with CloudPrintURLFetcher. 4) makes unit tests of CloudPrintURLFetcher, URLFetcher and URLRequest work. BUG=none TEST=pass all existing tests and also the newly-added request_throttler_unittest.cc Review URL: http://codereview.chromium.org/5276007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67375 0039d316-1c4b-4281-b951-d872f2087c98
* Export the new sessionid property of Chrome Frame form the NPAPI interface.rogerta@chromium.org2010-11-248-3/+100
| | | | | | | | | BUG=0 TEST=see included unit test Review URL: http://codereview.chromium.org/5331003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67311 0039d316-1c4b-4281-b951-d872f2087c98
* Add named testing interface. This allows you to connect to a pre-existing ↵nirnimesh@chromium.org2010-11-245-7/+17
| | | | | | | | | | | | | | | | | | | | | 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
* Temporarily disable selenium test for Chrome Frameamit@chromium.org2010-11-241-2/+2
| | | | | | | | | | | | | | ... and in the meantime figure out how to configure Selenium checkout on bots. TBR=ananta BUG=none TEST=FullTabSeleniumTest.Core Review URL: http://codereview.chromium.org/5314007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67268 0039d316-1c4b-4281-b951-d872f2087c98
* Test Selenium core on chrome frameamit@chromium.org2010-11-247-9/+95
| | | | | | | | | | | | | | | | | First cut of Selenium core support on Chrome Frame. 2 tests fail. Selenium tests are now served by mock http server. When the test is finished it posts a message with number of tests ran and failures. Also fixed 'attach external tab' mechanism to include the same URL origin including the port. BUG=50372 TEST=FullTabSeleniumTest.Core Review URL: http://codereview.chromium.org/5371001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67264 0039d316-1c4b-4281-b951-d872f2087c98
* Reconstructing 67000.bradnelson@google.com2010-11-232-2/+2
| | | | | | | | | | | | | | (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-222-2/+2
| | | | | | | | | | 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-222-2/+2
| | | | | | | | | 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
* Revert "Revert "net: Plumb DnsCertProvenanceChecker around.""agl@chromium.org2010-11-222-3/+10
| | | | | | (See r66623 for details.) git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66985 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "net: Plumb DnsCertProvenanceChecker around."agl@chromium.org2010-11-222-10/+3
| | | | | | This reverts commit r66970. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66974 0039d316-1c4b-4281-b951-d872f2087c98
* net: Plumb DnsCertProvenanceChecker around.agl@chromium.org2010-11-222-3/+10
| | | | | | (Reland of r66623, reverted in r66687 due to Chrome Frame linking issues.) git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66970 0039d316-1c4b-4281-b951-d872f2087c98
* Upload data when Stopping the service.hansl@google.com2010-11-221-0/+2
| | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/5103006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66922 0039d316-1c4b-4281-b951-d872f2087c98
* Allow specifying build configuration for poor man's trybot.joi@chromium.org2010-11-211-6/+21
| | | | | | | | | | TEST=none BUG=none Review URL: http://codereview.chromium.org/5225004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66917 0039d316-1c4b-4281-b951-d872f2087c98
* Always use flag needed by CEEE. Now that we use the same profile forjoi@chromium.org2010-11-213-19/+22
| | | | | | | | | | | | | | | | 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
* FBTF: Remove unneeded headers from base/ (part 9)thestig@chromium.org2010-11-201-2/+0
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/5091005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66873 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 66840 - Add named testing interface. This allows you to connect to a ↵kkania@chromium.org2010-11-205-18/+9
| | | | | | | | | | | | | | | | | | | | | | | | 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-195-9/+18
| | | | | | | | | | | | | | | | | | | | | 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
* Automating the poor man's trybot.joi@chromium.org2010-11-193-68/+85
| | | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/5137008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66824 0039d316-1c4b-4281-b951-d872f2087c98
* Add a PRESUBMIT.py for Chrome Frame. As many of the checks will be commonjoi@chromium.org2010-11-191-0/+26
| | | | | | | | | | | | | across CF and CEEE, this just reuses the ceee_presubmit.py file with some special-casing to avoid checks written for CEEE that do not apply to CF. BUG=none TEST=none Review URL: http://codereview.chromium.org/5162007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66815 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "net: Plumb DnsCertProvenanceChecker around."agl@chromium.org2010-11-182-10/+3
| | | | | | | This reverts commit r66623. Some how it causes libnspr4.dll to be linked in Chrome Frame builds. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66687 0039d316-1c4b-4281-b951-d872f2087c98
* Enable boot-time prefetching for Chrome Frame for all dev and CEEE channels ↵robertshield@chromium.org2010-11-181-20/+33
| | | | | | | | | | | on XP only (where there's no superfetch). BUG=None TEST=None Review URL: http://codereview.chromium.org/5138003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66639 0039d316-1c4b-4281-b951-d872f2087c98
* net: Plumb DnsCertProvenanceChecker around.agl@chromium.org2010-11-182-3/+10
| | | | | | | | | | | | | | | | | | | | | | | DnsCertProvenanceChecker is introduced to abstract away the action of uploading reports. It's implemented by ChromeDnsCertProvenanceChecker which lives in a scoped_ptr off of a URLRequestContext. It's only active on the main context (i.e. not in incognito mode). This might change in the future, but it's a nice, conservative choice for the moment. The DnsCertProvenanceChecker is plumbed all the way to SSLClientSocket (via HttpCache) where it replaces the DnsRRResolver. Above SSLClientSocket, it's plumbed in addition to the DnsRRResolver because the later will end up going into SSLHostInfo in the future. At the moment, ChromeDnsCertProvenanceCheckerContext is just a skeleton to avoid putting too much real code in a plumbing job. BUG=none TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66623 0039d316-1c4b-4281-b951-d872f2087c98
* Ensure that popup windows opened within ChromeFrame full tab mode in IE ↵ananta@chromium.org2010-11-181-2/+12
| | | | | | | | | | | | | | | | receive the desired content are size. To achieve this we first set the desired window styles on the web browser and then query it for the effective width and height. Fixes bug http://code.google.com/p/chromium/issues/detail?id=60447 Bug=60447 Test=Covered by existing window open tests. Review URL: http://codereview.chromium.org/5128002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66569 0039d316-1c4b-4281-b951-d872f2087c98
* Change the FF CEEE to create its chrome frame instance initially hidden, androgerta@chromium.org2010-11-183-90/+92
| | | | | | | | | | | | | | | | | | | make it visible only once the content is done loading. This avoids any flicker at startup, and fixes a bug where the chrome frame instance is removed after a print preview. Also added support to chrome frame to send an uninitialized ready state when its being torn down. Did some cleanup in the chrome frame tests which were broke the first time this change was committed. BUG=62979 TEST=Make sure that there is no UI flicker on chrome frame startup, and make sure that the extenions works correct after showing print preview and closing it. Review URL: http://codereview.chromium.org/5022003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66552 0039d316-1c4b-4281-b951-d872f2087c98
* Make use of the new version flag in Chrome to load the correct chrome.dll ↵robertshield@chromium.org2010-11-172-8/+15
| | | | | | | | | | | | | | version. Also fix a memory leak in the Chrome Frame automation code. BUG=61609 TEST=Chrome.exe always loads the specified chrome.dll when run by Chrome Frame. Review URL: http://codereview.chromium.org/5090001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66462 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 66350 - Add named testing interface. This allows you to connect to a ↵nirnimesh@chromium.org2010-11-173-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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-173-2/+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@66350 0039d316-1c4b-4281-b951-d872f2087c98
* Remove a DCHECK when failing to secure the shared memory used to hold the ↵robertshield@chromium.org2010-11-161-3/+4
| | | | | | | | | | | current version. This may well fail on older (read non-NTFS) systems since you can't secure file mappings without a securable file system underneath. BUG=61609 TEST=No DCHECKing at startup when running on a non-NTFS system. Review URL: http://codereview.chromium.org/5057007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66322 0039d316-1c4b-4281-b951-d872f2087c98
* Fix the ChromeFrame FullTabModeIE_TestDownloadFromForm test flakiness on IE9.ananta@chromium.org2010-11-161-0/+2
| | | | | | | | TBR=amit Review URL: http://codereview.chromium.org/4980004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66311 0039d316-1c4b-4281-b951-d872f2087c98
* Remove FLAKY_ from ChromeFrameActivex.ShouldShowVersionMismatchDialogjoi@chromium.org2010-11-161-2/+1
| | | | | | | | | | | | | | | test. The errors we were seeing on the builders were transient, due to an IID change. I checked the last 5 runs of the 3 CF builders on the waterfall just now, and also earlier today, and the test passes on all of these runs. TEST=none BUG=62636 Review URL: http://codereview.chromium.org/5070001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66276 0039d316-1c4b-4281-b951-d872f2087c98
* The UI language rather than the locale is now used to pick Chrome's language ↵grt@chromium.org2010-11-163-123/+34
| | | | | | | | | | | | | | | on Windows. (Also fixed some unrelated lint errors.) With this change, l10n_util::GetApplicationLocale first checks for an override of the "configured locale" (in base::i18n) containing the list of preferred Windows UI languages. The browser triggers an override early in startup before the ApplicationLocale is determined. In effect, the browser no longer uses ICU on Windows for language detection. (This locale override mechanism is borrowed from the OS X port.) Changes in Chrome Frame are largely a refactor, as some Win32 code in there has been moved into base/win. Also cleaned up language selection in installer_util so that the proper language is chosen for the EULA, installer messages, and shortcuts. In so doing, replaced hand-crafted lists of supported languages with either auto-generated lists (static consts) or logic so that the addition of translations in the future doesn't require code motion (that being said, there may be reason to update the alias and/or wildcard tables in language_selector.cc). In so doing, this change unlocks Amharic, Farsi, and Swahili translations for installer messages and shortcuts. BUG=39986,40496,26470 TEST=New MUI/Win32 calls are tested in base/win/i18n_unittest.cc. To test the overall functionality, uninstall Chrome, remove intl.app_locale user pref, switch to a supported display language (via the "Keyboards and Languages" tab of Win7's "Regional and Language" control panel, and install with { "distribution": { "require_eula": true } } in master_preferences (via -installerdata arg to setup.exe). If all goes well, both EULA and outer frame are in the same language as Windows. Also, from gwilson: "Install system-level Chrome in audit mode on a new machine, then go through the out-of-box-experience, select a language, and the in -product EULA (triggered by "require_eula" : true) and Chrome's UI should be in the language that the user selected." Review URL: http://codereview.chromium.org/4139010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66275 0039d316-1c4b-4281-b951-d872f2087c98
* Chrome Frame: Add explicit object security attributes to the Chrome Frame ↵robertshield@chromium.org2010-11-163-14/+221
| | | | | | | | | | | | | version beacon. This will allow low integrity processes to access shared memory segment and lock and make shared memory segment read only after creation. Also use lock names that include the hosting process. BUG=61609 TEST=Start medium integrity Chrome Frame host running CF version X. Update CF to version Y > X. Start low integrity Chrome Frame host, observe that version X is loaded. Review URL: http://codereview.chromium.org/5012001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66270 0039d316-1c4b-4281-b951-d872f2087c98
* Fix more ChromeFrame tests so that they work on IE9.ananta@chromium.org2010-11-153-3/+5
| | | | | | Review URL: http://codereview.chromium.org/4983004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66193 0039d316-1c4b-4281-b951-d872f2087c98
* Not running the following Chromeframe tests on IE9. This will enable the ↵ananta@chromium.org2010-11-152-5/+23
| | | | | | | | | | | | | | | | | | | builder to now run the tests to completion and hopefully turn green. 1. CF_DownloadFileFromPost. This test expects to see a File save dialog. On IE9 the prompt to save the file is displayed as a link on the frame window. 2. WidgetModeIE_CFInstancePost, WidgetModeIE_CFInstanceRPC, WidgetModeIE_CFInstanceRPCInterna These tests fail on IE9. Needs more investigation. TBR=amit Review URL: http://codereview.chromium.org/4998003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66158 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-07 19:33:26 +0000