Drag and dropping text, parsable as url

ui/base/DEPS

Index: ui/base/DEPS
diff --git a/ui/base/DEPS b/ui/base/DEPS
index acac72efa5490e3b58af7af7749bf8bbe0cf6c58..d81e04fbd5eb8d8e4427a80d578b60ca77be7ae0 100644
--- a/ui/base/DEPS
+++ b/ui/base/DEPS
@@ -12,4 +12,5 @@ include_rules = [
   "+ui/resources/grit/webui_resources.h",
   "+ui/strings/grit/app_locale_settings.h",
   "+ui/strings/grit/ui_strings.h",
+  "+components/url_formatter/url_fixer.h",

[dyaroshev, 2016/09/14 17:12:05]

Where is the correct place to put drag_and_drop_url_utils? url_formatter and
ui/base are independent right now

[Peter Kasting, 2016/09/15 21:26:53]

I asked sky to comment here, he might know better.

[sky, 2016/09/15 21:32:50]

Components is a huge directory, and once you add this dependency two bad things
could happen. url_formatter could get a dependency we don't want in ui/base and
it won't readily be obvious to the person making the change. Second it confuses
things from a mental model of what components is. By that I mean where does
components sit in the layer tree of dependencies? From the developers
perspective it's nice to think of components layering on top of ui/base, but
that wouldn't be the case if you do that. For theses reasons ui/base shouldn't
depend upon components.

I see two options. Don't put ui/base/dragdrop/drag_and_drop_url_utils.h in
ui/base, or move url_formatter into ui/base. Moving url_formatter into ui/base
doesn't feel the greatest, but ui/base is already a bit of a dumping ground for
functionality like this.

 ]