Andreas Tolfsen ❲:ato❳ Assignee
	Description • 7 years ago

The sizemodechange event is not strongly connected to the
visibilitychange event that the WPT minimize_window.py test is
now using to ascertain whether the window has been successfully
iconified.

Because Marionette uses the sizemodechange event it is
causing intermittents such as https://bugzil.la/1397007.  You
can also read a lengthy summary I did on the problem in
https://bugzil.la/1397007#c11.

The fix for the problem is to wait for the visibilitychange DOM
event content.

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 1 • 7 years ago

The sizemodechange event is not strongly connected to the
visibilitychange event that the WPT minimize_window.py test is now
using to ascertain whether the window has been successfully iconified.

Because Marionette uses the sizemodechange event it is causing
intermittents such as https://bugzil.la/1397007.  You can also read a
lengthy summary I did on the problem in https://bugzil.la/1397007#c11.

The fix for the problem is to wait for the visibilitychange DOM
event content.

MozReview-Commit-ID: B6i33Ee5iMC

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 2 • 7 years ago

try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f83a6d597a90fd32006e3d0370b675944c27ee3f

	Henrik Skupin [:whimboo][⌚️UTC+1]
	Comment 3 • 7 years ago

Comment on attachment 8910282 [details] [diff] [review]
Wait for visibilitychange event on window minimize/restore. r?whimboo

Review of attachment 8910282 [details] [diff] [review]:
-----------------------------------------------------------------

A mozreview request would be nicer, maybe you plan one now that the dependency has been fixed. Until then a question I would like see answered first. Thanks.

::: testing/marionette/driver.js
@@ +3720,2 @@
>   */
> +async function restoreWindow(chromeWindow, contentWindow) {

Why can't we add this method to the BrowserContext class, which has both the information for chrome and content window available, and IMO would be a better fit for this feature.

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 4 • 7 years ago

(In reply to Henrik Skupin (:whimboo) from comment #3)
> ::: testing/marionette/driver.js
> @@ +3720,2 @@
> >   */
> > +async function restoreWindow(chromeWindow, contentWindow) {
> 
> Why can't we add this method to the BrowserContext class, which
> has both the information for chrome and content window available,
> and IMO would be a better fit for this feature.

This will get moved to a class similar in nature to browser.Context
with http://bugzil.la/marionette-window-tracking, but considering
none of the other window manipulation helpers are there, it makes
sense to leave it in its current place for now.

	Andreas Tolfsen ❲:ato❳ Assignee
	Comment 5 • 7 years ago

Comment on attachment 8910282 [details] [diff] [review]
Wait for visibilitychange event on window minimize/restore. r?whimboo

Can we get this patch landed soon so that we can resolve
https://bugzil.la/1397007?

	Pulsebot
	Comment 6 • 7 years ago

Pushed by atolfsen@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6470a12114de
Wait for visibilitychange event on window minimize/restore. r=whimboo

	Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)
	Comment 7 • 7 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/6470a12114de