"WebDriver:ElementClick" for <option> fires mouse events without expected parameters
Categories
(Remote Protocol :: Marionette, defect, P3)
Tracking
(Not tracked)
People
(Reporter: canadahonk, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webdriver:backlog])
Attachments
(1 file)
The mouse events fired when doing "WebDriver:ElementClick" on an <option> element does not include the expected parameters of the mouse events fired (button
, buttons
, position, etc).
We should likely switch to using event.synthesizeMouseAtPoint
instead of event.mousedown
/etc in this case.
Comment 1•2 years ago
|
||
(In reply to CanadaHonk [:canadahonk] from comment #0)
We should likely switch to using
event.synthesizeMouseAtPoint
instead ofevent.mousedown
/etc in this case.
We have a specific order of events that we fire when simulation the selection of an option. So if event.synthesizeMouseAtPoint
is emitting the same events it might be fine, but otherwise we might have to set all the required fields in opts
when calling the different mouse events directly. Note that you would also have to take bug 1550680 into account here.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:whimboo, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 3•2 years ago
|
||
CanadaHonk, would you be interested to help with this particular bug? It's blocking the other bug that you are working on and I'm not sure when I / we would get to this one. As usual I would assist where-ever I can. Thanks a lot.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 5•1 year ago
|
||
Previously mouse events fired when an <option> is clicked did not
include extra expected parameters (eg button
).
Updated•1 year ago
|
Comment 6•10 months ago
|
||
Oliver, would you have a chance to check my review comments which require an update of the patch? Thanks.
Reporter | ||
Comment 7•6 months ago
|
||
Sorry, I don't have the cycles to work on these patches at the moment.
Comment 8•3 months ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Description
•