TestForcedFullscreen.test_user_exit_swipe_up fails on devices

[Olivier Tilloy]

webbrowser_app.tests.test_fullscreen.TestForcedFullscreen.test_user_exit_swipe_up started failing on devices running the latest rc-proposed around yesterday (2015-12-14).

There was a big unity8 (and related components) landing happening on 2015-12-11, so it’s most likely what caused the regression.

The actual browser functionality seems unaffected, as I can make the test succeed by manually swiping in the bottom edge (which is what the test is trying and failing to do), so it’s only a matter of fixing the test itself.

[Olivier Tilloy (osomon)]

And the fix for bug #1422523 could very well be what is causing the failure.

When invoking the drag_bottom_edge_upwards() method, I’m seeing that the coordinates differ when the window is fullscreen (failing test) and when it’s not (other tests that pass):

  fullscreen: swiping from 1818 to 430
  not fullscreen: swiping from 1887 to 499

that’s on arale.

[Olivier Tilloy (osomon)]

It appears that windows that request fullscreen do not get fullscreen any longer (this can be observed with any webapp that passes the --fullscreen command-line parameter, such as Zombies TD), that’s most likely a regression introduced by the unity8 (and related components) landing last Friday. Hopefully fixing that issue will make the failure go away.

[Olivier Tilloy (osomon)]

This is probably bug #1525893.