New issue
Advanced search Search tips

Issue 687732 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Modal dialogs, when run from tests, do not activate browser windows

Project Member Reported by jochen@chromium.org, Feb 1 2017

Issue description

on non-mac platforms, if an alert() is shown, chrome::FindLastActive() will return that browser, but on mac, it won't.

This makes it hard to write tests on mac for this, e.g., see https://codereview.chromium.org/2661403003/#ps60001
 
Cc: thakis@chromium.org
Cc: -a...@chromium.org
Owner: a...@chromium.org
Status: Assigned (was: Unconfirmed)
help us avi@, you're our only hope :)

Comment 3 by a...@chromium.org, Nov 3 2017

Summary: Modal dialogs, when run from tests, do not activate browser windows (was: when a browser is raised due to a modal dialog, it's not marked as active)
To find our answer, look at chrome/test/base/interactive_test_utils_mac.mm's ShowAndFocusNativeWindow(). What we learn is that because test processes are not bundled, the macOS does not allow them to get focus.

ShowAndFocusNativeWindow() goes through a LOT OF WORK to make this work for a test binary, work that is neither necessary nor desired for alert dialogs which are not test-only.

The easy answer to all of this is that activation is being removed from alerts. When that is done, all the uses of ui_test_utils::BrowserActivationWaiter that fail with alerts are in tests that will be removed and this bug will be moot.

Comment 4 by a...@chromium.org, Jun 8 2018

Status: WontFix (was: Assigned)
Mooted with  bug 849816 ; alerts no longer activate anyway.

Sign in to add a comment