Performing key down/up actions fail for a pdf.js test that awaits for the "keyup" event
Categories
(Remote Protocol :: WebDriver BiDi, defect, P1)
Tracking
(Not tracked)
People
(Reporter: whimboo, Assigned: Sasha)
References
Details
(Whiteboard: [webdriver:m9])
Attachments
(1 file)
7.92 KB,
patch
|
Details | Diff | Splinter Review |
The test that is failing is part of freetext_editor_spec.mjs
and the particular lines can be found here:
When running the test I can see that Backspace
is actually sent because the input's value is cleared, but the evaluation Promise doesn't resolve because no keyup
event is emitted by the pageNumber input. Running the same test with CDP works fine.
Steps to run the test:
- Clone https://github.com/mozilla/pdf.js
- Run
npm install
. - Apply the changes from https://github.com/mozilla/pdf.js/pull/17172/files
- Define a custom binary via the
executablePath
field in the options - Open
freetext_editor_spec.mjs
and usefdescribe("Avoid to steal keyboard events", () => {
in line 2984. - Run the integration test with
gulp integrationtest --noChrome
To check why it's only failing in BiDi I've created both a WebDriver test (see attachment) and a Marionette test, but both are passing. So I'm not sure what exactly is causing this test to fail.
Reporter | ||
Comment 1•1 year ago
|
||
Sasha, could you please have a look at? Thanks.
Reporter | ||
Comment 2•1 year ago
|
||
Because it is blocking the pdf.js tests lets make it a M9 bug.
Assignee | ||
Updated•1 year ago
|
Reporter | ||
Comment 3•1 year ago
|
||
The related upstream PR is https://github.com/mozilla/pdf.js/pull/17378.
Assignee | ||
Comment 4•1 year ago
|
||
The fix is actually now being worked on by pdf.js team in the scope of https://github.com/mozilla/pdf.js/pull/17387.
:whimboo, should we maybe then close this bug, or you would prefer to keep it?
Reporter | ||
Comment 5•1 year ago
|
||
Even the pdf.js team works on it we did all the investigation which took some time. As such lets close this bug once the pdf.js issue is fixed.
Reporter | ||
Comment 6•1 year ago
|
||
This is fixed now.
Description
•