ubuntu-webapps-bugs team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

Marked this bug fixed, and filed bug #1490907 to track the need for a
unit test that verifies that the position is expressed in physical
pixels.

** Changed in: oxide
       Status: In Progress => Fix Released

** Changed in: oxide
    Milestone: None => 1.9.1

** Changed in: oxide
    Milestone: 1.9.1 => branch-1.10

** Also affects: oxide/1.9
   Importance: Undecided
       Status: New

** Changed in: oxide/1.9
    Milestone: None => 1.9.1

** Changed in: oxide/1.9
     Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: oxide/1.9
   Importance: Undecided => Medium

** Changed in: oxide/1.9
       Status: New => Fix Committed

-- 
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:
  Fix Released
Status in Oxide 1.9 series:
  Fix Committed

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