Firefox overlay is seen opened even if Import Overlay is Cancelled.

chrome/browser/ui/views/importer/import_lock_dialog_view.cc

Index: chrome/browser/ui/views/importer/import_lock_dialog_view.cc
diff --git a/chrome/browser/ui/views/importer/import_lock_dialog_view.cc b/chrome/browser/ui/views/importer/import_lock_dialog_view.cc
index 061fceb48ea3a6ac4271d93e229ccfcf97703c79..52125c60482830bab4430f83c91d86739b64f3fb 100644
--- a/chrome/browser/ui/views/importer/import_lock_dialog_view.cc
+++ b/chrome/browser/ui/views/importer/import_lock_dialog_view.cc
@@ -30,13 +30,30 @@ void ShowImportLockDialog(gfx::NativeWindow parent,
   content::RecordAction(UserMetricsAction("ImportLockDialogView_Shown"));
 }
 
+void HideImportLockDialog() {
+  ImportLockDialogView::Hide();
+}
+
 }  // namespace importer
 
+// For storing widget ptr on creation of dialog widget
+// using method CreateDialogWidget.
+namespace {
+static views::Widget* g_widget = nullptr;
+}
+
+// static
+void ImportLockDialogView::Hide() {
+  if (g_widget)
+    g_widget->Close();

[Ilya Sherman, 2017/03/30 22:14:32]

Should you set g_widget to nullptr here?

[nikhil.sahni, 2017/03/31 15:21:25]

Done.

+}
+
 // static
 void ImportLockDialogView::Show(gfx::NativeWindow parent,
                                 const base::Callback<void(bool)>& callback) {
-  views::DialogDelegate::CreateDialogWidget(
-      new ImportLockDialogView(callback), NULL, NULL)->Show();
+  g_widget = views::DialogDelegate::CreateDialogWidget(
+      new ImportLockDialogView(callback), NULL, NULL);
+  g_widget->Show();
 }
 
 ImportLockDialogView::ImportLockDialogView(
@@ -80,6 +97,7 @@ base::string16 ImportLockDialogView::GetWindowTitle() const {
 bool ImportLockDialogView::Accept() {
   base::ThreadTaskRunnerHandle::Get()->PostTask(FROM_HERE,
                                                 base::Bind(callback_, true));
+  g_widget = nullptr;

[Ilya Sherman, 2017/03/30 22:14:32]

What about if the user cancels the dialog instead?  I think it's safer to listen
for the notification, in case there's any other way for the dialog to be closed,
than trying to catch every possible individual code path.

[nikhil.sahni, 2017/03/31 15:21:25]

In case of CANCEL even the IMPORT Dialog gets closed as import is Cancelled so
in this case
there is no possibility for the user to explicitly cancel that.

I also studied views::WidgetObserver class,
I can implement soemthing like below

void ImportLockDialogView::OnWidgetDestroying(views::Widget* widget) {
  g_widget = nullptr;
}
 
but have to do  AddObserver here , I am stuck as where to do that here .

Can you please guide me on this, thanks 

[Ilya Sherman, 2017/04/04 05:39:52]

Yes, I think implementing ImportLockDialogView::OnWidgetDestroying() is the best
approach.  Please implement it as

void ImportLockDialogView::OnWidgetDestroying(views::Widget* widget) {
  g_widget = nullptr;
  widget->RemoveObserver(this);
}

You can call g_widget->AddObserver() as part of the ImportLockDialogView::Show()
function.  To do so, you'll need to capture the "new
ImportLockDialogView(callback)" in a local variable.

If you implement this approach, you then don't need any of the "g_widget =
nullptr" lines below, which is a lot less fragile to edge cases and code
refactoring.

[nikhil.sahni, 2017/04/04 09:21:40]

Done.

   return true;
 }