Update chromium code to use WebIntentRequest.

content/renderer/render_view_impl.h

Index: content/renderer/render_view_impl.h
diff --git a/content/renderer/render_view_impl.h b/content/renderer/render_view_impl.h
index 22a555fbff39552d742e64408c51e867736321fa..5a1a00f9d8c5764fdc49c55d26c2e66b80a5080a 100644
--- a/content/renderer/render_view_impl.h
+++ b/content/renderer/render_view_impl.h
@@ -528,7 +528,7 @@ class RenderViewImpl : public RenderWidget,
       WebKit::WebFrame* frame,
       const WebKit::WebIntentServiceInfo& service);
   virtual void dispatchIntent(WebKit::WebFrame* frame,
-                              const WebKit::WebIntent& intent);
+                              WebKit::WebIntentRequest* intent);

[James Hawkins, 2012/01/12 00:11:58]

Just curious, why does this need to come through as a pointer instead of
const-ref?

[Greg Billock, 2012/01/12 18:54:45]

Yeah, we're talking about that on the webkit CR. Basically we need the
refcounted WebCore::IntentRequest this thing holds. So I could use a copy
constructor with a const ref, or pass it like this. This way looks more explicit
to me as an ownership transfer, so I wrote it that way, but a copy constructor
would work equally well, and cause some niceness in default empty
implementations.

[James Hawkins, 2012/01/12 19:07:36]

Up to you, was just curious.

 
   // WebKit::WebPageSerializerClient implementation ----------------------------