touch-packages team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

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.

** Changed in: webbrowser-app (Ubuntu)
       Status: New => Triaged

** Changed in: webbrowser-app (Ubuntu)
     Assignee: (unassigned) => Olivier Tilloy (osomon)

** Tags added: autopilot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1526364

Title:
  TestForcedFullscreen.test_user_exit_swipe_up fails on devices

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1526364/+subscriptions