Use StringView for startsWith and endsWith.

third_party/WebKit/Source/core/frame/csp/CSPSource.cpp

Index: third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
diff --git a/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp b/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
index b4283a13f7a3968de43ad915b335f1d7721270b7..cb520195db732f469bbc8ccbe83b605b27efe705 100644
--- a/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
+++ b/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
@@ -53,7 +53,7 @@ bool CSPSource::hostMatches(const KURL& url) const
 
     bool equalHosts = equalIgnoringCase(host, m_host);
     if (m_hostWildcard == HasWildcard) {
-        match = host.endsWith("." + m_host, TextCaseInsensitive);
+        match = host.endsWith(String("." + m_host), TextCaseInsensitive);

[esprehn, 2016/07/13 23:42:55]

a + b returns a StringAppend, which can't be converted to a StringView. We can
fix this by declaring template<A, B> startsWith(StringAppend<A, B> string) const
{ return startsWith(String(string)); } but I want to save that for another patch
if/when we need it. This is the only place anyone concats a string before
calling these methods today and making the allocation explicit doesn't seem too
bad.

 
         // Chrome used to, incorrectly, match *.x.y to x.y. This was fixed, but
         // the following count measures when a match fails that would have