Add --force-first-run-dialog, regression tests for r511312.
Chrome has a modal first-run dialog displayed during browser startup on Linux and Mac, before the main MessageLoop begins. It is supressed under many scenarios, and completely disabled in Chromium builds, making it very difficult to test (even manually). Before r511312 Chrome would upload a crash dump if a SIGTERM or similar was received while the dialog was showing on Mac. This CL adds --force-first-run-dialog which works in official and non- official builds for testing the dialog manually. Adds a regression test for r511312 to test signal handling while this dialog is showing. This also gives some bot coverage of the dialog code. Consolidates repeated and redundant logic leading up to the dialog invocation, allowing Linux/Mac to share the --force-first-run-dialog logic as well. The behaviour of the run loop used while the modal dialog runs also changed in r511673, which could cause Chrome to ignore SIGTERM while the dialog was showing. That's not ideal, so handle this as well. Bug: 777660 Change-Id: I523966003eda01d43f15d0217e075e11838da38a Reviewed-on: https://chromium-review.googlesource.com/734381Reviewed-by:Greg Thompson <grt@chromium.org> Commit-Queue: Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#517337}
Showing
Please register or sign in to comment