#107 ✓invalid

Easy autocompleter indicator?

Reported by KronosZZ | October 28th, 2008 @ 06:14 PM

(sorry for my english, I'm spanish)


I found a way to do autompleter indicator easier writing the HTML without "indicator" SPAN. You just must to assign a class to the field related.


<input type="text" id="autocomplete" name="autocomplete_parameter" class=\"ac_field\"/>
<div id="autocomplete_choices" class="autocomplete"></div>


INPUT.ac_field {background-image:url(/images/ac_leftcap.gif);background-position:right center;background-repeat:no-repeat;}
INPUT.ac_field_busy {background-image:url(/images/ac_spinner.gif);background-position:right center;background-repeat:no-repeat;}

CONTROLS.JS (changes between lines 121 - 130)

startIndicator: function() {
   //if(this.options.indicator) Element.show(this.options.indicator);

stopIndicator: function() {
   //if(this.options.indicator) Element.hide(this.options.indicator);

That's all! :)

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket