Hi ColinI studied the code a bit, and it seems its somewhat different for the Ajax.Autocompleter compared to the Local.Autocompleter. To understand what really happens I've tried to wrap up some of the important events.
1) The ajax request will run onComplete when done, and if you look in the code,
ColinI've sort of done this with a Local.Autocompleter (show text and hide ID, submit ID when item is selected).In order to do this you need to override the methods that write the resultdiv and the method that run when an item is selected.
You can override any method of the Ajax.Autocompleter by si
I've successfully implementet resultdiv with scrolling. it works very well in IE and FF, but since it doesnt work in Safari, the patches have not been applied to the script.aculo.us library :-/
I'm not on Mac so its hard for me to make it work in Safari.Tommy S
-Original Message-From: [EMAI
The key up will make the page scroll to the top of the inputfield... I've seen this myself and the reason is the changes applied in this patch:http://dev.rubyonrails.org/ticket/4782
I am pretty sure it is because of this statement:this.getEntry(this.index).scrollIntoView(true); the "true"-makes the
I dont think its is allowed according to the W3C standards to have sections inside the . Keep that in mind when insering css-style-sections. ;-)
-Tommy
[Rails-spinoffs] RE: Leak in the Autocompleter, with scrollable result-div ?
Hi EdThe reason it adds a new onblur is because when you click the scrollbar the event is gone. I dont know why and how to prevent it, but without adding it back the onblur does not get triggered and the layer does not hide when you click somewhere else on the page. If anyone finds a better solutio
Hi everyone
If you've seen this ticket, http://dev.rubyonrails.org/ticket/4782,
you've noticed I have tried to make scrollable autocompleter work. The
scrollIntoView works great, however the iframefix for IE didnt work in
the previous change. This is fixed now.
Also the "blur-on-scrollbar-click" s
