Auto complete with AHAH: Clicking button vs hitting Enter

Drupal's Forms API AHAH implementation only works with buttons AFAIK. Putting it on other elements so that the enter button would have an effect has caused some really dodgy behaviour.

It might be possible to integrate some 3rd party jquery or something to make it happen? Don't know.

I used the following JS code in my theme to do this. AjaxComplete callback is to rebind the object if the AHAH feature is used.

$(document).ready(function() {
  _form_enterkey_ahah();
  $(document).ajaxComplete(_form_enterkey_ahah);
});

function _form_enterkey_ahah() {
  $(".finder-form input.form-autocomplete").unbind("keypress").bind("keypress", function(e) {
    if (e.which == 13) {
      $(".finder-form #edit-submit").trigger("mousedown");
      return false;
    }
  });
}

Has anyone had any success with the above code? It seems to only work if you:
1) Are using an autocomplete element.
2) You are not using 'submit upon selection'.
3) Select the autocomplete suggestion with your MOUSE
4) For some unfathomable reason you then press 'enter' on a KEYBOARD.

:(

Besides, there is nothing actually wrong about the way it currently works. If you 'tab' over to the submit button and press enter, it works perfectly - that is the correct way to use it.

ok so I didn't see 'auto complete' in the issue title, that explains 1).

I also noticed it assumes the submit button has an ID of #edit-submit which it often doesn't.

I've also looked into using ahah_helper as suggested on the page linked in post #2, but that module didn't appear to do anything :/ I'd ask on their issue queue but it looks like nobody has answered issues there in a while.

I have a similar problem. I've turned off the autocomplete feature by simply using a regular text box with the "find" button turned on. If I click the find button with the mouse, ahah worked fine. If I hit return after entering my search text, then it opens in a new page. I'll try out some of hte code above and see if it works for me.

Whoohoo!! I got it to work!! :)

2 Changes: e.keyCode instead of e.which and trigger('click') instead of trigger ('mousedown').

<script type="text/javascript">
      $(document).ready(function() {
    	  _form_enterkey_ahah();
    	  $(document).ajaxComplete(_form_enterkey_ahah);
    	});

    	function _form_enterkey_ahah() {
        $(".finder-form input.form-autocomplete").unbind("keypress").bind("keypress", function(e) {

    	    if (e.keyCode == 13) {
        	  $(".finder-form #edit-submit").trigger('click');
    	      return false;
    	    }
    	  });
    	}
    </script>

Thank you gundarx - without your code I wouldn't have been able to even *start* figuring this out.

Question: Is it possible to make this part of the finder project? I'm not an expert on jquery, so I wouldn't know if there are some potential conflicts with other parts of the js code.

No problem. I'm happy to contribute where I can :)

Question: Is it possible to make this part of the finder project?

The code assumes there is only one finder form on a page, and it assumes things about there being a button and what the properties of that button are, and nobody has stated clearly under what circumstances this script would be added to the output. I think it needs work or at least these things should be addressed.