Remove assertion from DetachToOwnWindow on macOS 10.10.

On macOS 10.10, AppKit appears to use the test's generated events to
asynchronously reactivate the first window. There's no way to tell when this
asynchronous reactivation will happen, so just avoid checking the assertion in
the test. This problem appears constrained to how we generate test events, and
not to the actual behavior of Chrome.

Bug: 862859
Change-Id: Ibab56946bef3aea9aac3123d3d8aefdb7974d063
Reviewed-on: https://chromium-review.googlesource.com/1135305
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574699}
1 file changed