Move //components/captive_portal into layered component structure
We will shortly be componentizing CaptivePortalService out of //chrome.
This class depends on the Content API and should only be used on
//content-based platforms, whereas the existing
//components/captive_portal is shared with iOS. This CL moves the
existing component into a layered component structure in anticipation
of imminently moving CaptivePortalService and friends into a //content
subdirectory.
There are no functional changes here; it is a strict code move.
[email protected]
Bug: 1030692
Change-Id: Id231098e56b5c3f28c921c0082918fdf669ebeac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010982
Commit-Queue: Colin Blundell <[email protected]>
Reviewed-by: Matt Menke <[email protected]>
Cr-Commit-Position: refs/heads/master@{#734392}
diff --git a/components/security_interstitials/content/BUILD.gn b/components/security_interstitials/content/BUILD.gn
index 59068b7..509cab3 100644
--- a/components/security_interstitials/content/BUILD.gn
+++ b/components/security_interstitials/content/BUILD.gn
@@ -52,7 +52,7 @@
":proto",
"//base",
"//build:branding_buildflags",
- "//components/captive_portal",
+ "//components/captive_portal/core",
"//components/network_time",
"//components/prefs:prefs",
"//components/resources",
