Skip to content

Conversation

@lindagruenwald
Copy link
Contributor

@lindagruenwald lindagruenwald commented Sep 20, 2023

When typing in an input field, the browser usually sends an input event with a specific inputType, e.g. "insertText" when adding characters, "deleteContentBackward" when backspacing, among others.

When using set or fill_in on a field, Cuprite is currently triggering the event in a way that leaves inputType as undefined, which is (unfortunately) what Chrome actually sends on autocompletion. The mostly correct way to trigger this event here should be with "insertText".

@route
Copy link
Member

route commented Sep 22, 2023

Let's see the tests ;)

@route route merged commit 7326bff into rubycdp:main Sep 22, 2023
@route
Copy link
Member

route commented Sep 22, 2023

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants