Hi,
on the autocomplete demo-page I've noticed many examples that set
"minChars" option to "0", giving the impression that they will fire up
as soon as each input field gets the focus. However, they don't, and I
have to type in at least one character to get the autocompletion
working. Now, since I'd really need to autocomplete fields when they
get focus, I'm wondering if I can get this in any way. Is autocomplete
expected to support this feature at any time in the future? If
autocomplete doesn't support this at all, how can I get a similar
result?
> Hi,
> on the autocomplete demo-page I've noticed many examples that set
> "minChars" option to "0", giving the impression that they will fire up
> as soon as each input field gets the focus. However, they don't, and I
> have to type in at least one character to get the autocompletion
> working. Now, since I'd really need to autocomplete fields when they
> get focus, I'm wondering if I can get this in any way. Is autocomplete
> expected to support this feature at any time in the future? If
> autocomplete doesn't support this at all, how can I get a similar
> result?
You are right, but sometimes it's nice to have a list of options
rolled down as soon as the field gets the focus. Especially when that
list is quite short (maybe as a consequence of some filtering based on
already filled in fields). In these cases, it'd be nice to have
autocomplete working without any input from the user. Using the same
widget for all the (text) input fields instead of many different ones
will end in a better user experience (IMHO).
> Isn't the entire idea behind auto_complete_ that it actually needs
> input before it can complete anything for you?
> On Mar 19, 10:37 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> > Hi,
> > on the autocomplete demo-page I've noticed many examples that set
> > "minChars" option to "0", giving the impression that they will fire up
> > as soon as each input field gets the focus. However, they don't, and I
> > have to type in at least one character to get the autocompletion
> > working. Now, since I'd really need to autocomplete fields when they
> > get focus, I'm wondering if I can get this in any way. Is autocomplete
> > expected to support this feature at any time in the future? If
> > autocomplete doesn't support this at all, how can I get a similar
> > result?
I am trying to get the same functionality as Andrea also.
Here's my use case:
I currently have a traditional form select drop down list that can get
very long. It's tedious to scan and scroll through the entire list
when it gets long.
I would like to use autocomplete to show the entire list on focus, and
then dynamically pare down the list as the user types in part of an
element name.
I think that would create the best user experience for my case.
Right now, it's confusing for a user to double click the input field
in order for the entire list of elements to show. Single click (aka
focus) doesn't work.
Ideas?
Thanks,
Ed
On Mar 19, 3:20 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> You are right, but sometimes it's nice to have a list of options
> rolled down as soon as the field gets the focus. Especially when that
> list is quite short (maybe as a consequence of some filtering based on
> already filled in fields). In these cases, it'd be nice to haveautocompleteworking without any input from the user. Using the same
> widget for all the (text) input fields instead of many different ones
> will end in a better user experience (IMHO).
> > Isn't the entire idea behind auto_complete_ that it actually needs
> > input before it can complete anything for you?
> > On Mar 19, 10:37 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> > > Hi,
> > > on theautocompletedemo-page I've noticed many examples that set
> > > "minChars" option to "0", giving the impression that they will fire up
> > > as soon as each input field gets the focus. However, they don't, and I
> > > have to type in at least one character to get the autocompletion
> > > working. Now, since I'd really need toautocompletefields when they
> > > get focus, I'm wondering if I can get this in any way. Isautocomplete
> > > expected to support this feature at any time in the future? If
> > >autocompletedoesn't support this at all, how can I get a similar
> > > result?
I have updated my local version of the plugin to support the behavior
that we both want.
In the unminified version 1.02 of the autocomplete plugin, change line
165
from:
if ( hasFocus++ > 1 && !select.visible() ) {
to:
if ( hasFocus++ > 0 && !select.visible() ) {
In my test on Firefox 3.x and iPhone safari, it worked fine. When you
single click into the field, your complete drop down list will now
show up, and autocomplete works correctly.
Hope this helps,
Ed
On Mar 19, 3:20 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> You are right, but sometimes it's nice to have a list of options
> rolled down as soon as the field gets the focus. Especially when that
> list is quite short (maybe as a consequence of some filtering based on
> already filled in fields). In these cases, it'd be nice to have
> autocomplete working without any input from the user. Using the same
> widget for all the (text) input fields instead of many different ones
> will end in a better user experience (IMHO).
> > Isn't the entire idea behind auto_complete_ that it actually needs
> > input before it can complete anything for you?
> > On Mar 19, 10:37 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> > > Hi,
> > > on the autocomplete demo-page I've noticed many examples that set
> > > "minChars" option to "0", giving the impression that they will fire up
> > > as soon as each input field gets the focus. However, they don't, and I
> > > have to type in at least one character to get the autocompletion
> > > working. Now, since I'd really need to autocomplete fields when they
> > > get focus, I'm wondering if I can get this in any way. Is autocomplete
> > > expected to support this feature at any time in the future? If
> > > autocomplete doesn't support this at all, how can I get a similar
> > > result?
> I have updated my local version of the plugin to support the behavior
> that we both want.
> In the unminified version 1.02 of the autocomplete plugin, change line
> 165
> from:
> if ( hasFocus++ > 1 && !select.visible() ) {
> to:
> if ( hasFocus++ > 0 && !select.visible() ) {
> In my test on Firefox 3.x and iPhone safari, it worked fine. When you
> single click into the field, your complete drop down list will now
> show up, and autocomplete works correctly.
> Hope this helps,
> Ed
> On Mar 19, 3:20 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> > You are right, but sometimes it's nice to have a list of options
> > rolled down as soon as the field gets the focus. Especially when that
> > list is quite short (maybe as a consequence of some filtering based on
> > already filled in fields). In these cases, it'd be nice to have
> > autocomplete working without any input from the user. Using the same
> > widget for all the (text) input fields instead of many different ones
> > will end in a better user experience (IMHO).
> > Any hints?
> > Andrea
> > On Mar 19, 10:48 am, bart <b...@ivwd.nl> wrote:
> > > Isn't the entire idea behind auto_complete_ that it actually needs
> > > input before it can complete anything for you?
> > > On Mar 19, 10:37 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> > > > Hi,
> > > > on the autocomplete demo-page I've noticed many examples that set
> > > > "minChars" option to "0", giving the impression that they will fire up
> > > > as soon as each input field gets the focus. However, they don't, and I
> > > > have to type in at least one character to get the autocompletion
> > > > working. Now, since I'd really need to autocomplete fields when they
> > > > get focus, I'm wondering if I can get this in any way. Is autocomplete
> > > > expected to support this feature at any time in the future? If
> > > > autocomplete doesn't support this at all, how can I get a similar
> > > > result?
> On Mar 30, 12:41 pm, Ed J <edwardo...@gmail.com> wrote:
> > Hi Andrea,
> > I have updated my local version of the plugin to support the behavior
> > that we both want.
> > In the unminified version 1.02 of the autocomplete plugin, change line
> > 165
> > from:
> > if ( hasFocus++ > 1 && !select.visible() ) {
> > to:
> > if ( hasFocus++ > 0 && !select.visible() ) {
> > In my test on Firefox 3.x and iPhone safari, it worked fine. When you
> > single click into the field, your complete drop down list will now
> > show up, and autocomplete works correctly.
> > Hope this helps,
> > Ed
> > On Mar 19, 3:20 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> > > You are right, but sometimes it's nice to have a list of options
> > > rolled down as soon as the field gets the focus. Especially when that
> > > list is quite short (maybe as a consequence of some filtering based on
> > > already filled in fields). In these cases, it'd be nice to have
> > > autocomplete working without any input from the user. Using the same
> > > widget for all the (text) input fields instead of many different ones
> > > will end in a better user experience (IMHO).
> > > Any hints?
> > > Andrea
> > > On Mar 19, 10:48 am, bart <b...@ivwd.nl> wrote:
> > > > Isn't the entire idea behind auto_complete_ that it actually needs
> > > > input before it can complete anything for you?
> > > > On Mar 19, 10:37 am, "Mr.Rech" <andrea.ricip...@gmail.com> wrote:
> > > > > Hi,
> > > > > on the autocomplete demo-page I've noticed many examples that set
> > > > > "minChars" option to "0", giving the impression that they will fire up
> > > > > as soon as each input field gets the focus. However, they don't, and I
> > > > > have to type in at least one character to get the autocompletion
> > > > > working. Now, since I'd really need to autocomplete fields when they
> > > > > get focus, I'm wondering if I can get this in any way. Is autocomplete
> > > > > expected to support this feature at any time in the future? If
> > > > > autocomplete doesn't support this at all, how can I get a similar
> > > > > result?
|
