testcafe
testcafe copied to clipboard
PressKey, meta and contenteditable
What is your Test Scenario?
We have the keyboard shortcut meta+i to italicize some text. We want to check that the text is well italicized.
What is the Current behavior?
A "i" is added after the meta+i is pressed.
What is the Expected behavior?
Meta+i should not add an i in the contenteditable event target.
What is your web application and your TestCafe test code?
Upcoming.
await t.pressKey("meta+i");
Please note we have no bug with ctrl or shift, it is specific to meta.
Your Environment details:
- testcafe version: 1.10
- node.js version: v14.0.0
- command-line arguments: none
- browser name and version: chrome 87
- platform and version: MacOS 10.14
It's difficult to find the cause of the problem without an example of a web page. Could you please give us a website url so that we can reproduce and research the issue on our side?
This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.
@Dmitry-Ostashev, I'm also hitting this issue and have created a minimal repo to display my issue: https://github.com/biw/testcafe-5810-example
To summarize the behavior I see vs. the behavior I'd expect:
Result (with extra 'i' from .pressKey("meta+i")
:
0: hi therei
1:
Expected:
0: hi there
1:
@biw Thank you for your example. I've reproduced the issue. We'll research it and we'll update this thread as soon as we have any news.
Awesome, thank you @Dmitry-Ostashev!
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.
We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.