Getting rid of DelegatedFrameData

cc/output/compositor_frame.cc

Index: cc/output/compositor_frame.cc
diff --git a/cc/output/compositor_frame.cc b/cc/output/compositor_frame.cc
index 82479cf3b43ab363fb4cd1b458754f10e8da1429..6a9d003b396105d44d61fd0016c8e277c1923448 100644
--- a/cc/output/compositor_frame.cc
+++ b/cc/output/compositor_frame.cc
@@ -14,4 +14,8 @@ CompositorFrame::~CompositorFrame() {}
 
 CompositorFrame& CompositorFrame::operator=(CompositorFrame&& other) = default;
 
+bool CompositorFrame::IsEmpty() const {
+  return render_pass_list.empty() && resource_list.empty();

[danakj, 2016/10/25 22:23:07]

I find this function weird..

1) resource_list is a set of things referred to in the render_pass_list. So it
has to be empty if render_pass_list is empty.

2) empty compositor frames exist before this patch and we don't branch on them
in places that this patch now does, so why is that what we want?

[Fady Samuel, 2016/10/26 03:13:55]

I agree we probably don't need this or just return render_pass_list.empty() and
DCHECK that resource_list.empty()) || !render_pass_list.empty()

[Saman Sami, 2016/10/26 14:41:18]

1) I'll fix it.
2) There are certain places that we check for empty frames. See
content/browser/android/synchronous_compositor_host.cc:146 for an example. Can
you be more specific about where I have introduced new branches? 

+}
+
 }  // namespace cc