#657 new

Autocompleter completes multiple times and screws up the completed value

Reported by David | September 4th, 2013 @ 02:40 PM

Hi everybody,

when using an autocompleter, completions are done multiple times and the value of the text field is not longer a suggested value.

Please have a look at this Screen recoding demonstrating the problem

What i did is:

  1. Prado TAutoComplete Example
  2. Typed "John" and pressed Enter.
  3. deleted "hn"
  4. pressed tab

It looks like it depends on the speed of your network connection and the speed of typing.

I tracked down the problem to the function "getTokenBounds" in controls.js:

   getTokenBounds: function() {
     if (null != this.tokenBounds) return this.tokenBounds;

Removing the whole "if"-Statement solves this problem for me, because it looks like the stored tokenBounds are not longer valid, because this.element.value has changed in the meanwhile.

No comments found

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