wrong object coordinates if the app goes fullscreen

[Olivier Tilloy]

While investigating autopilot test failures in gallery-app on Ubuntu Touch (see bug #1422418), I observed that a menu was being open, and the wrong menu item was being pressed (the item below the targetted one was being pressed). I realized that what seemed to have introduced the regression was a change in the app whereby it would go fullscreen at a given point in time during its execution. When the app goes fullscreen on Ubuntu Touch, the top indicators bar disappears, thus moving the window upwards by 41px (on krillin)). It seems that when the app does that, autopilot gets the coordinates for objects on screen as if the window hadn’t moved, and therefore clicks don’t happen where they are expected. Could it be that the absolute coordinates of the window are cached and not updated when it goes fullscreen?

[Olivier Tilloy (osomon)]

Just confirmed my suspicion by printing the app’s main view globalRect property before it goes fullscreen and after:

  - before: Rectangle(0, 41, 540, 919)
  - after: Rectangle(0, 41, 540, 960)

It appears the height is correctly updated, but not the y coordinate.

[Gerry Boland (gerboland)]

qtubuntu a likely cause yeah. mir apps are not informed of their window position on screen, so I've hacky heuristics in qtubuntu to guess window positioning, which AP uses to calculate absolute input coordinates. Those heuristics not aware of window state change probably

[Olivier Tilloy (osomon)]

This is related to bug #1346633. QtMir needs to use the API introduced in Mir to find the surface position relative to the screen.

[Florian Boucault (fboucault)]

Affects the camera-app now.

[Daniel d'Andrada (dandrader)]

Could you please check if https://code.launchpad.net/~dandrader/qtubuntu/enhancePanelHack/+merge/278799 solves the issue?

[Daniel d'Andrada (dandrader)]

Can't use the mentioned Mir API just yet.