cc: Shrink size of display item

cc/trees/layer_tree_host_pixeltest_tiles.cc

Index: cc/trees/layer_tree_host_pixeltest_tiles.cc
diff --git a/cc/trees/layer_tree_host_pixeltest_tiles.cc b/cc/trees/layer_tree_host_pixeltest_tiles.cc
index ec2303ae6b65fea439b381e5f9a049454587ea39..8c2d0e38bb9731ad936eb1efd8d458ccd4e5f3c5 100644
--- a/cc/trees/layer_tree_host_pixeltest_tiles.cc
+++ b/cc/trees/layer_tree_host_pixeltest_tiles.cc
@@ -133,10 +133,8 @@ class BlueYellowClient : public ContentLayerClient {
     skia::RefPtr<SkPicture> picture =
         skia::AdoptRef(recorder.endRecordingAsPicture());
 
-    auto* item = display_list->CreateAndAppendItem<DrawingDisplayItem>(
-        PaintableRegion());
-    item->SetNew(std::move(picture));
-
+    display_list->CreateAndAppendItem<DrawingDisplayItem>(PaintableRegion(),
+                                                          std::move(picture));

[vmpstr, 2015/12/04 00:43:09]

For all these 

skia::RefPtr<SkPicture> picture = stuff;
...(..., std::move(picture));

i wonder if it would just be cleaner to

...(..., stuff); directly? Or do you think this is cleaner?

[danakj, 2015/12/04 00:53:54]

When you get a pointer from skia APIs the first thing you do with it is put it
in a skia::RefPtr.

[vmpstr, 2015/12/04 01:24:28]

"stuff" would include skia::AdoptRef()

[danakj, 2015/12/04 01:24:54]

Ooh ok that'd be fine. :)

     display_list->Finalize();
     return display_list;
   }