Move navigation interception component to content/components

chrome/chrome_tests.gypi

Index: chrome/chrome_tests.gypi
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi
index 7909716934a3af03dc38ef78ec0e6d9798f10455..0275b9fb1df520aaa0535caf2e6c170c22621b13 100644
--- a/chrome/chrome_tests.gypi
+++ b/chrome/chrome_tests.gypi
@@ -1246,7 +1246,7 @@
         'browser/chromeos/version_loader_unittest.cc',
         'browser/chromeos/web_socket_proxy_helper_unittest.cc',
         'browser/command_updater_unittest.cc',
-        'browser/component/navigation_interception/intercept_navigation_resource_throttle_unittest.cc',
+        '../content/components/navigation_interception/intercept_navigation_resource_throttle_unittest.cc',

[Jói, 2012/10/31 21:18:27]

Add a TODO here to move tests to content/components/content_components.gyp.  I
think we can do this as a follow-up because we need to establish a new unittest
executable first, and add it to bot configurations so it runs on trybots and
such.

I doubt we want tests from content/components to be part of content_unittests,
although maybe I'm wrong.  John (jam@) could perhaps chime in.

[John Knottenbelt, 2012/11/02 14:48:25]

Done.

[jam, 2012/11/02 16:57:56]

(just saw this)

I'm fine having a separate step later to move them into a separate target. but i
would really prefer that nothing moves into content/components with chrome
dependencies. this should be easy to remove per my other comment

         'browser/component_updater/component_updater_interceptor.cc',
         'browser/component_updater/component_updater_interceptor.h',
         'browser/component_updater/test/component_installers_unittest.cc',