Content API changes to improve DOM stitching in ThreatDetails code.

components/safe_browsing/common/safebrowsing_messages.h

Index: components/safe_browsing/common/safebrowsing_messages.h
diff --git a/components/safe_browsing/common/safebrowsing_messages.h b/components/safe_browsing/common/safebrowsing_messages.h
index 1e03fa10f4504a6ebd48dd7a2ea3e7e6c4ab1167..95d9c09c6bc44cb206f8f4ef9f55a9fe37145e5e 100644
--- a/components/safe_browsing/common/safebrowsing_messages.h
+++ b/components/safe_browsing/common/safebrowsing_messages.h
@@ -40,6 +40,11 @@ IPC_STRUCT_BEGIN(SafeBrowsingHostMsg_ThreatDOMDetails_Node)
 
   // The node's attributes, as a collection of name-value pairs.
   IPC_STRUCT_MEMBER(std::vector<safe_browsing::AttributeNameValue>, attributes)
+
+  // If this node represents a frame or iframe, then this field is set to the
+  // routing ID of the local or remote frame in this renderer process that is
+  // responsible for rendering the contents of this frame (to handle OOPIFs).
+  IPC_STRUCT_MEMBER(int, child_frame_routing_id)

[estark, 2017/05/24 00:42:35]

I'm not sure it matters too much in this case, but
https://dev.chromium.org/Home/chromium-security/education/security-tips-for-i....
says this should be an explicitly sized integer type.

[lpz, 2017/05/24 14:31:39]

Done, and thanks for the handy link!

 IPC_STRUCT_END()
 
 // SafeBrowsing client-side detection messages sent from the renderer to the