Repository navigation
Calling Node#set with empty string doesn't trigger the input event #156
Description
Hi, thank you for building this great gem, it's so nice not to have to go through selenium and chromedriver 🙏🏻
When switching to Cuprite, I noticed that calling Node#set with an empty string doesn't trigger the input event. In my app I'm using Stimulus to listen to input event on a search field, and triggering requests when the field value changes. I had code like this:
visit "/products"
find("#query").set("Foo") # input event is correctly triggered
expect(page).to have_current_path("/products?q=Foo")
find("#query").set("") # input event is not triggered
expect(page).to have_current_path("/products?q=") # it's still on /products?q=FooHere is a self-contained example showing the input event is not being triggered:
require "roda"
class App < Roda
plugin :render, layout: false
route do |r|
r.root do
render(inline: <<~HTML)
<html>
<head></head>
<body>
<input type="text" id="field" />
<div id="events"></div>
<script>
document.querySelector('#field').addEventListener('input', function() {
document.querySelector('#events').append(document.createTextNode('input event'))
})
</script>
</body>
</html>
HTML
end
end
end
require "capybara/cuprite"
Capybara.current_driver = :cuprite
Capybara.register_driver :cuprite do |app|
Capybara::Cuprite::Driver.new(app, js_errors: true)
end
session = Capybara::Session.new(:cuprite, App)
session.visit "/"
session.find("#field").set("value")
puts session.find("#events").text
session.find("#field").set("")
puts session.find("#events").textIs there some other idiomatic way for clearing the field? I noticed that Selenium triggers some special clearing when an empty string is passed in to Node#set.
Activity
tomekchime commentedon Feb 21, 2024
This looks related to #238. Curious if you were able to find a workaround @janko?
janko commentedon Feb 21, 2024
@tomekchime I don't remember from the top of my head, I think I just triggered the
inputevent manually, possibly by callingtrigger(:input)on the node.route commentedon Oct 15, 2026
Fixed in #336 (same bug as #164): clearing a non-empty text field with
node.set("")/fill_in "field", with: ""now dispatches aninputevent (inputType: "deleteContentBackward") beforechange, so thetrigger(:input)workaround is no longer needed. It will ship in the next release; until then you can usemain.