Open Bug 1490258 Opened 4 years ago Updated 2 months ago

Remove moz:useNonSpecCompliantPointerOrigin


(Testing :: Marionette, enhancement, P3)



(Not tracked)


(Reporter: ato, Unassigned)


(Depends on 1 open bug, Blocks 1 open bug)


This bug tracks the removal of the temporary
moz:useNonSpecCompliantPointerOrigin capability.

From the description in geckodriver’s README:

> A boolean value to indicate how the pointer origin for an action
> command will be calculated.
> With Firefox 59 the calculation will be based on the requirements
> by the WebDriver specification. This means that the pointer origin
> is no longer computed based on the top and left position of the
> referenced element, but on the in-view center point.
> To temporarily disable the WebDriver conformant behavior use false
> as value for this capability.
> Please note that this capability exists only temporarily, and that
> it will be removed once all Selenium bindings can handle the new
> behavior.
Blocks: 1489130
Priority: -- → P3
Can you give any indication which Selenium bindings we are waiting for?
Flags: needinfo?(hskupin)
Sorry, but I don't know the status at the moment. It's been a while since we added that, and I doubt that much has been changed for the bindings given that we didn't file any issue. At some point we should re-evaluate it all.

Note that there are still left-open bugs which fail without this capability. We should do a triage session maybe during our upcoming workweek to hash out those dependencies.
Flags: needinfo?(hskupin)
I can’t find any reference to moz:useNonSpecCompliantPointerOrigin
in the Selenium repository [1] which means clients are not employing
this workaround in a centralised fashion and that—by default—the
stock behaviour users get is equal to the default WebDriver-conforming
behaviour geckodriver ships with.

This means there’s a likelihood that a small amount of users use
this capability to make their action tests pass, but that a vast
majority of them think their action tests are broken in Firefox
because of a bug in geckodriver.  I wonder if not the best approach
would be to not offer a workaround to Selenium and instead track
the bug to fix the underlying problem.

However, I don’t know what, or where, the underlying problem is
being tracked in Selenium. 

You won't find it there, right. But consumers of Selenium have this capability set to workaround some known bugs in Marionette (as mentioned before), and maybe because they are lazy to update the tests for the new behavior.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.