Comments on: Autocomplete Migration Guide

By: 10 Awesome jQuery Autocomplete Plugins & Tutorials | codeManiac - Snippets, Templates, API and the best developer content

Wed, 25 Apr 2012 18:11:25 +0000

[...] Autocomplete Migration Guide [...]

By: jQuery Autocomplete

jQuery Autocomplete — Thu, 12 Jan 2012 02:22:28 +0000

[...] This plugin is deprecated and not developed anymore. Its successor is part of jQuery UI, and this migration guide explains how to get from this plugin to the new one. This page will remain as it is for reference, [...]

By: jQuery UI Autocomplete ‘autoFill’ and/or ‘selectFirst’ feature. How to? | DEEP in PHP

Mon, 14 Feb 2011 00:03:40 +0000

[...] http://www.learningjquery.com/2010/06/autocomplete-migration-guide [...]

By: Dylan

Dylan — Tue, 14 Sep 2010 17:25:25 +0000

A quick question. Is there a number of records limit for autocomplete?

I am displaying some data from the database and IE8, Firefox, Safari and Chrome all work fine with 110,00 records – but for some reason I am getting Out of memory error in IE6 and IE7. If I limit number of records to 50,000 it works in IE6 and IE7.

Any ideas what’s going on?

BTW I am using the old version, does anyone knows if upgrading to new version will fix this?

Thanks!

By: Daniel

Daniel — Tue, 14 Sep 2010 08:07:20 +0000

hi,
How do i limit the number of results displayed in the suggestion.I used max:20 but its not working . And i am passing Array which contains json data as the source to the autocomplete and by default it does contains operation , i want startswith , How do i achieve this. Can somebody help me out.
Thanks

By: Jörn Zaefferer

Jörn Zaefferer — Fri, 10 Sep 2010 20:24:47 +0000

Yeah, in this case changing the source is the best option. Once you’re done with the migration you’d remove the renamed one anyway.

By: MaT

MaT — Fri, 10 Sep 2010 13:21:54 +0000

Is it possible, somehow, to have both versions active at the same time? They are both called by .autocomplete… I want to change to newer version in my application, but it is very complex, I will have to change a lot and I think that doing it progressively will be easier for me…

Should I change the function name in js source?

By: Kerr

Kerr — Tue, 31 Aug 2010 13:53:45 +0000

Jörn – Thanks for your continued efforts! I’ve used your autocomplete plugin for a couple years now, and have been watching the jQuery UI based plugin with great interest. Today I implemented the new plugin across all of my sites, and while it took some adjustment, I see the wisdom in all the changes that were made. On the whole, my autocomplete calls are much more terse while still carrying the same functionality. I also like that I can simply apply CSS styles for the different states.

By: Andrew

Andrew — Thu, 26 Aug 2010 22:48:32 +0000

I completely agree with Sebastian, please do not underestimate the power of this feature. As far as I can see the extension does not behave the same as the original. It should "highlight" the option and not "select" it until the user presses TAB or ENTER, as per the default behaviour on your original demo page. I love your old extension Jörn but won't be migrating until this is resolved. Does anyone have any alternative solutions? Thanks.

By: Frederik

Frederik — Wed, 18 Aug 2010 14:15:30 +0000

Example of what to use instead of matchContains:false would be nice :)