GitLab

The setTimeout with 0 delay caused notifyDone() to sometimes be called
too early. Instead add an event listener in the non-isolated world that
should be triggered when the media query changes and add an extra rAF()
in case the event listener is called first for the non-isolated world
handler.

The test still fails though, so the *expected.txt, which is now the same
for all platforms, needs to be kept.

The tests were marked with Timeout. If it turns out it is still slow on
some bots, we can add it to SlowTests.

The media query event handler argument had changed since the test was
written, so fixed the test itself as well.

Bug: 390452
Change-Id: I31c370601d932152adeb16bdffc59e4b68a2907d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2041476Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#739087}