Open tomasmatus opened 1 week ago
Can you reproduce this locally? If so, can you please paste a full run with --trace
? I just checked def mouse()
, and
if ctrlKey:
keys_pre.append(key("keyDown", "Control"))
keys_post.append(key("keyUp", "Control"))
seems correct to me, I don't see typos. In the log I'd like to see that the "keyUp Control" is actually ran. If so, then it rather smells like a firefox bug. Do you know, is that only Control, or also affects Alt/Shift/Meta?
Another example which is still around is https://github.com/cockpit-project/cockpit-files/blob/main/test/check-application#L819
Explain what happens
When using
b.mouse()
with ctrl key modifier in Firefox the modifier is kept active for all futureb.mouse()
calls.I am not sure if this is a bug in testlib or something in firefox bidi driver.
Relevant testing farm failure: https://artifacts.dev.testing-farm.io/650d6b68-b518-414e-9ff2-d2b8f8d73939/
Relevant part of testNavigation: First in the test ctrl modifier is used
and then later on in the test there is another use of
b.mouse
this time with ctrlKey=False (default). Testingfarm log shows the test fails here.problem also persists when explicitly setting it to false in the function call.
The bidi input action looks good to me.
Version of Cockpit
327
Where is the problem in Cockpit?
None
Server operating system
None
Server operating system version
No response
What browsers are you using?
Firefox
System log
No response