1795984 - Put browser fullscreen tests under its own folder

Status: NEW

(Core :: DOM: Core & HTML, task)

Comment 1

[Edgar Chen [:edgar]]

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

Comment 2

[Edgar Chen [:edgar]]

Attachment: Bug 1795984 - Put browser fullscreen tests under fullscreen folder; r?Gijs

Comment 3

[Edgar Chen [:edgar]]

Attachment: Bug 1795984 - Put DOM fullscreen test under its own folder; r?smaug

Depends on D159633

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f742568d925b
Put browser fullscreen tests under fullscreen folder; r=Gijs
https://hg.mozilla.org/integration/autoland/rev/4f1f5ebc134b
Put DOM fullscreen test under its own folder; r=smaug

Comment 5

[Norisz Fay [:noriszfay]]

Backed out for causing bc failures on browser_fullscreen-window-open.js, browser_fullscreen_api_fission.js

Backout link

Push with failures

Failure log 1 // Failure log 2

Comment 6

[Edgar Chen [:edgar]]

The changes for browser tests cause some test failures, I think they seems to be a known issue, see bug 1595896 and bug 987115, and moving it to a different folder somehow make it becomes a perma failure. Lets try to land the DOM part in a separated bug.

Comment 7

[Phabricator Automation]

Comment on attachment 9299109 [details]
Bug 1795984 - Put DOM fullscreen test under its own folder; r?smaug

Revision D159634 was moved to bug 1798274. Setting attachment 9299109 [details] to obsolete.

Comment 8

[BugBot [:suhaib / :marco]]

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:edgar, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.

Comment 9

[Edgar Chen [:edgar]]

Need to figure out comment 6 first.