Fix implementation of the startup notification protocol for the main instance
At the moment, the implementation of the startup notification protocol [1] does only make sure that the window manager gets notified when the startup process finishes for non-primary instances of the main process, that is, when the user attempts to spawn a new chromium-browser process while another instance is already running. This is because ProcessSingleton::NotifyOtherProcessWithTimeout() is the only placed where NotifyWindowManagerStartupComplete() is being called, which used to be fine when chromium relied on GTK+ for its top-level windows (GTK+ calls gdk_display_notify_startup_complete() when mapping the top-level window) in the past, but now that chromium relies on Aura, it's necessary to add another explicit call in the codepath that completes startup for the main instance. [1] https://www.freedesktop.org/wiki/Specifications/startup-notification-spec Bug: 553956 Change-Id: Ie9bf2db9bc04589229a18785771b6fc97dbcc9bd Reviewed-on: https://chromium-review.googlesource.com/1072088Reviewed-by:Lei Zhang <thestig@chromium.org> Reviewed-by:
David Reveman <reveman@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#565390}
Showing
Please register or sign in to comment