Add suborigin logic to url::Origin

content/public/common/url_constants.h

Index: content/public/common/url_constants.h
diff --git a/content/public/common/url_constants.h b/content/public/common/url_constants.h
index 1a90cf2414c2109dd93a6b4376aa0c679ae44aee..3448a883319ee24b89d1777bd68db1465b53d182 100644
--- a/content/public/common/url_constants.h
+++ b/content/public/common/url_constants.h
@@ -72,11 +72,6 @@ CONTENT_EXPORT extern const char kChromeUINetworkViewCacheURL[];
 CONTENT_EXPORT extern const char kChromeUIResourcesURL[];
 CONTENT_EXPORT extern const char kChromeUIShorthangURL[];
 
-// Special HTTP and HTTPS schemes for serialization of suborigins. See
-// https://w3c.github.io/webappsec-suborigins/.
-CONTENT_EXPORT extern const char kHttpSuboriginScheme[];
-CONTENT_EXPORT extern const char kHttpsSuboriginScheme[];

[Mike West, 2016/10/11 07:40:41]

If we're moving in this direction, we really ought to file a bug against URL and
HTML to see about upstreaming this change. It's pointing to a pretty tight
integration of suborigins with origins themselves in terms of parsing,
serialization, comparison, etc.

[jww, 2016/10/11 18:16:27]

Indeed, that was a suggestion by Anne in the serialization spec issue. I have a
TODO for potential URL integration. I'm still not convinced it's the right way
to go, though.

-
 }  // namespace content
 
 #endif  // CONTENT_PUBLIC_COMMON_URL_CONSTANTS_H_