Public bug reported:
>From looking at the code in Chromium that is used to bring up the
context menu, it's not clear whether the position is in the source
frame's coordinate space, or the WebView one. It's also not clear
whether it's in physical or device-independent pixels.
It should be in the WebView coordinate space, and in physical pixels.
Testing this sort-of depends on bug 1399207, which will make it easier
to add new test runs with arbitrary configurations (such as a non-unity
device scale).
** Affects: oxide
Importance: Medium
Status: Triaged
** Changed in: oxide
Importance: Undecided => Medium
** Changed in: oxide
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1471181
Title:
Test that WebContextMenu position property is in the correct
coordinate space
Status in Oxide Webview:
Triaged
Bug description:
From looking at the code in Chromium that is used to bring up the
context menu, it's not clear whether the position is in the source
frame's coordinate space, or the WebView one. It's also not clear
whether it's in physical or device-independent pixels.
It should be in the WebView coordinate space, and in physical pixels.
Testing this sort-of depends on bug 1399207, which will make it easier
to add new test runs with arbitrary configurations (such as a non-
unity device scale).
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1471181/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
