Closed Bug 1752203 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 32561 - Window Placement: Await visibilitychange in WPT for resolved bounds

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox99 fixed)

Status:
RESOLVED FIXED
Milestone:
99 Branch
Tracking Flags:
Tracking Status
firefox99 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(Depends on 1 open bug,
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 32561 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/32561
Details from upstream follow.

Mike Wasserman <msw@chromium.org> wrote:

Window Placement: Await visibilitychange in WPT for resolved bounds

Check resolved popup window bounds after its Document.visibilitychange.
This is a better signal than window.load + a 300ms timeout.

Bug: 1022988
Test: Automated (and manual) WPT.
Change-Id: I7a3ad78c3b344ac9fb9b79558fac62820e3d4556
Reviewed-on: https://chromium-review.googlesource.com/3415320
WPT-Export-Revision: c4a64bd358137bb3d3a257e385323e7861ed23a0

PR 32561 applied with additional changes from upstream: 16c49f7b9752b3d859823ab0de9d5fe2de113a3e, bcfd973869839b7a5ad579bd8cbc12c0b4d7bb9b, f8925dd8a1e6154aace065b0a757f322b0dcbad6
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bb8b3b8db347 [wpt PR 32561] - Window Placement: Await visibilitychange in WPT for resolved bounds, a=testonly
Test result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/948fdb621c8b [wpt PR 32561] - Window Placement: Await visibilitychange in WPT for resolved bounds, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/948fdb621c8b

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox99: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.