Navigation transitions: Parse out transition-entering-stylesheet link headers.

content/browser/transition_request_manager.h

Index: content/browser/transition_request_manager.h
diff --git a/content/browser/transition_request_manager.h b/content/browser/transition_request_manager.h
index 9ef969b49dba26cbdaad5a97f9df2c9161a3133a..10cc03baedd60a5ed99aa5d4816773bf4ea37b78 100644
--- a/content/browser/transition_request_manager.h
+++ b/content/browser/transition_request_manager.h
@@ -7,15 +7,29 @@
 
 #include <set>
 #include <utility>
+#include <vector>
 
 #include "base/basictypes.h"
+#include "base/memory/ref_counted.h"
 #include "content/common/content_export.h"
+#include "url/gurl.h"
 
 template <typename T>
 struct DefaultSingletonTraits;
 
+namespace net {
+  class HttpResponseHeaders;

[jochen (gone - plz use gerrit), 2014/07/16 13:25:59]

don't indent

[Zhen Wang, 2014/07/18 00:56:35]

Done.

+}
+
 namespace content {
 
+struct TransitionLayerData {
+  TransitionLayerData();

[jochen (gone - plz use gerrit), 2014/07/16 13:25:59]

please inline ctor/dtor here.

[Zhen Wang, 2014/07/18 00:56:35]

If I inline them, the compiler will complain with error message:

"error: [chromium-style] Complex constructor has an inlined body."


On 2014/07/16 13:25:59, jochen wrote:

+  ~TransitionLayerData();
+
+  std::vector<GURL> transition_stylesheets;
+};
+
 // TransitionRequestManager is used to handle bookkeeping for transition
 // requests and responses.
 //
@@ -27,6 +41,13 @@ class TransitionRequestManager {
   // Returns the singleton instance.
   CONTENT_EXPORT static TransitionRequestManager* GetInstance();
 
+  // Parses out any transition-entering-stylesheet link headers from the
+  // response headers.
+  static void ParseTransitionStylesheetsFromHeaders(
+      scoped_refptr<net::HttpResponseHeaders> headers,
+      TransitionLayerData& transition_layer_data,
+      const GURL& resolve_address);
+
   // Returns whether the RenderFrameHost specified by the given IDs currently
   // has a pending transition request. If so, we will have to delay the
   // response until the embedder resumes the request.