autocomplete can't be tested

[myfitment]

I realize that there are some open issues around this, but while some people have claimed to have solved this, I have found it to be impossible. My assertions for the presence of the jQuery autocomplete fields always fail, regardless of what events I trigger. Even calling the autocomplete field manually generates nothing. The code works flawlessly when tested in the browser.

After 40 hours straight of trying to troubleshoot this one line, I am wondering if anyone else has overcome the issue of Poltergeist not being able to test the jQuery UI autocomplete.

[myfitment]

I've determined that autocomplete is indeed firing, and is returning a result. However, when debugging via Poltergeist I find that Poltergeist is timing out while waiting for the autocomplete result HTML to generate.

[mikebaldry]

I got this working once, using key events to simulate someone typing.. if you just set the value, the events don't fire and the autocomplete doesn't show.. (at least in my case)

[superchris]

element.native.send_keys worked for me

[cshaffer]

+1 for native.send_keys. Using twitter's typeahead.js

[aprescott]

I think send_keys is the answer here and it seems like autocomplete can be tested. Looks like we can close this.

[h4b00]

hmm send_keys didn't work for me, anyone have example code?

[mmrwoods]

This is working for me, with both poltergeist/phantomjs and selenium/firefox...

def fill_in_autocomplete(selector, query)
  find(selector).native.send_keys(*query.chars)
end

phantomjs 1.9.7, poltergeist 1.5.1

[joxxoxo]

I'm also unable to make it work with send_keys :(
phantomjs 2.0.0, poltergeist 1.6.0, jQuery UI Autocomplete 1.11.4

UP: It's actually working, sorry. Didn't work during I was in the pry session, worked after I've left the debugger

[TommyF87]

@mmrwoods thanks for this solution, it works nicely.