[Background Sync] Sent sync registration details to worker

content/renderer/background_sync/background_sync_client_impl.cc

Index: content/renderer/background_sync/background_sync_client_impl.cc
diff --git a/content/renderer/background_sync/background_sync_client_impl.cc b/content/renderer/background_sync/background_sync_client_impl.cc
index 997b47650adfab276f505bedbbfbc03a8fc7dc6b..2eb1c40019da279279e19a5813eef0786524426b 100644
--- a/content/renderer/background_sync/background_sync_client_impl.cc
+++ b/content/renderer/background_sync/background_sync_client_impl.cc
@@ -4,7 +4,9 @@
 
 #include "content/renderer/background_sync/background_sync_client_impl.h"
 
+#include "content/child/background_sync/background_sync_type_converters.h"
 #include "content/renderer/service_worker/service_worker_context_client.h"
+#include "third_party/WebKit/public/platform/modules/background_sync/WebSyncRegistration.h"
 
 namespace content {
 
@@ -28,7 +30,9 @@ void BackgroundSyncClientImpl::Sync(content::SyncRegistrationPtr registration,
     callback.Run(SERVICE_WORKER_EVENT_STATUS_ABORTED);
     return;
   }
-  client->DispatchSyncEvent(callback);
+  scoped_ptr<blink::WebSyncRegistration> reg =
+      mojo::ConvertTo<scoped_ptr<blink::WebSyncRegistration>>(registration);

[jkarlin, 2015/07/17 20:28:10]

I think ConvertTo could return a blink::WebSyncRegistration without loss of
performance.

[iclelland, 2015/07/20 18:40:22]

The type converter is used in other places; is it worth chasing them all down
for this CL?

[jkarlin, 2015/07/20 18:46:25]

Hmm, just the provider and the unit tests. Seems reasonably small. But you can
TODO it for another CL if you prefer.

+  client->DispatchSyncEvent(*reg, callback);
 }
 
 }  // namespace content