-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node.trigger(:input)
doesn't dispatch an input
event
#197
Comments
Additionally, shouldn't this event have a property like: |
jcoyne
added a commit
to sul-dlss/happy-heron
that referenced
this issue
Aug 18, 2022
Cuprite doesn't have events that are implemented correctly. See rubycdp/cuprite#197
jcoyne
added a commit
to sul-dlss/happy-heron
that referenced
this issue
Aug 18, 2022
Cuprite doesn't have events that are implemented correctly. See rubycdp/cuprite#197
peetucket
pushed a commit
to sul-dlss/happy-heron
that referenced
this issue
Jun 13, 2023
Cuprite doesn't have events that are implemented correctly. See rubycdp/cuprite#197
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From following the JavaScript code, I believe that
node.trigger(:input)
currently ends up callingthis.dispatchEvent('input')
. However, that isn't the correct way to dispatch this event, it should bethis.dispatchEvent(new Event('input'))
.That's presumably the reason why the
Cuprite
JavaScript class defines a specialinput()
function, instead of callingtrigger()
.cuprite/lib/capybara/cuprite/javascripts/index.js
Lines 182 to 186 in 2bbf363
The text was updated successfully, but these errors were encountered: