We are accessing the //extension module from different parts of the
code, just to verify whether an url has an extension scheme. There was
a first try to refactor this logic in r889472 implementing an scheme
registration in blink::SchemeRegistry; this is implemented in the
renderer::platform module, so we can't access from the //content
module in order to keep browser / render isolation.
We need to determine whether an url uses chrome-extension scheme from
both, the Browser and Renderer process, hence it's sensible that this
logic would be moved to blink/common. This implies that we must use
std types instead of platform/wtf (eg. std::string).
BUG=1197375
Change-Id: I9143f14de5e5cd84f58e36b0d185822fd41f692c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3006218
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#909313}
03816ca3bd