Create Bookmark Footnote desktop iOS promotion

ui/views/bubble/bubble_frame_view.cc

Index: ui/views/bubble/bubble_frame_view.cc
diff --git a/ui/views/bubble/bubble_frame_view.cc b/ui/views/bubble/bubble_frame_view.cc
index c97fcf3eacc14dc428e4629fb94da1bcd6c5416a..f23cc758b62ed758fa46020dbce9ee87a57287b9 100644
--- a/ui/views/bubble/bubble_frame_view.cc
+++ b/ui/views/bubble/bubble_frame_view.cc
@@ -408,6 +408,16 @@ void BubbleFrameView::SetFootnoteView(View* view) {
   AddChildView(footnote_container_);
 }
 
+void BubbleFrameView::RemoveFootnoteView() {

[sky, 2017/05/17 16:00:41]

Instead of an explicit function like this, override ViewHierarchyChanged() and
if the view is the single child of footnote_container_ then delete
footnote_container_. If you do this, it means you can just delete the
footnote_view (or remove it from its parent), and the right thing will happen.
Add test coverage of this.

[mrefaat, 2017/05/17 19:44:56]

I remember that we talked about that and you said its also acceptable to have an
explicit function to do the footnote remove, is there an advantage for the
viewHierarchyChanged change over having explicit function to do that ?

[sky, 2017/05/18 02:55:38]

Sorry if I mislead you. It's a similar argument to why you don't have to remove
a view from its parent before deleting it. To do otherwise is error prone. It's
a common expectation that if you remove/delete the necessary cleanup is just
done.

[mrefaat1, 2017/05/23 22:15:34]

Done.

+  if (!footnote_container_)
+    return;
+
+  RemoveChildView(footnote_container_);
+  footnote_container_->RemoveAllChildViews(true);
+  delete footnote_container_;
+  footnote_container_ = nullptr;
+}
+
 gfx::Rect BubbleFrameView::GetUpdatedWindowBounds(const gfx::Rect& anchor_rect,
                                                   const gfx::Size& client_size,
                                                   bool adjust_if_offscreen) {