Skip to content
Snippets Groups Projects
  1. Dec 24, 2010
  2. Dec 23, 2010
  3. Nov 22, 2010
  4. Nov 10, 2010
  5. Nov 01, 2010
  6. Oct 27, 2010
  7. Jul 29, 2010
  8. Jun 03, 2010
  9. Jun 01, 2010
  10. May 27, 2010
  11. May 26, 2010
  12. May 25, 2010
  13. May 20, 2010
  14. May 19, 2010
  15. Apr 29, 2010
  16. Apr 08, 2010
  17. Mar 26, 2010
  18. Mar 14, 2010
  19. Mar 08, 2010
  20. Feb 25, 2010
  21. Feb 04, 2010
  22. Dec 05, 2009
  23. Nov 25, 2009
  24. Nov 08, 2009
    • joi@chromium.org's avatar
      Modifying extension automation so that it is done through a particular · 4cfc1d92
      joi@chromium.org authored
      tab for all extension views.  Previously, API routing to the
      automation client would only work for extension views that were
      contained in the particular ExternalTab instance being automated. This
      meant you couldn't test API calls from e.g. background pages.
      
      Also using async functions instead of the previous RVH-based hack.
      
      Updating one of the UI tests to make the API calls from a background
      page, to provide an end-to-end test of the new routing.
      
      This makes AutomationProvider::SetEnableAutomationExtension
      Windows-only, but it effectively always was since it was already
      dependent on ExternalTabContainer (indirectly, to provide a non-empty
      implementation of TabContentsDelegate::ForwardMessageToExternalHost).
      
      BUG=none
      TEST=ui_tests.exe, chrome_frame_tests.exe, chrome_frame_unittests.exe
      
      Review URL: http://codereview.chromium.org/366025
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31403 0039d316-1c4b-4281-b951-d872f2087c98
      4cfc1d92
  25. Oct 28, 2009
  26. Oct 23, 2009
  27. Oct 19, 2009
  28. Oct 06, 2009
  29. Sep 22, 2009
  30. Sep 11, 2009
  31. Aug 29, 2009
  32. Aug 28, 2009
  33. Aug 22, 2009
  34. Aug 20, 2009
  35. Jul 31, 2009
  36. Jul 16, 2009
Loading