heh, that is 10kb more of javascript to maintain.... -igor
On Wed, Apr 23, 2008 at 12:40 PM, Johan Compagner <[EMAIL PROTECTED]> wrote: > i really dont care about a 3kb or 13kb script .. > Those are cached anyway so thats fine by me > its not that it its 100kb+ or something like that > > johan > > > On Wed, Apr 23, 2008 at 8:34 PM, Gerolf Seitz <[EMAIL PROTECTED]> > wrote: > > > > > i _could_ use something from a combobox i did some time ago: > > > http://people.apache.org/~gseitz/combo/<http://people.apache.org/%7Egseitz/combo/> > > <http://people.apache.org/%7Egseitz/combo/> > > but that script is 13kb (unstripped) compared to wicket-autocomplete > > 3k (stripped) and it's based on YUI... > > > > On Wed, Apr 23, 2008 at 4:49 PM, Gerolf Seitz <[EMAIL PROTECTED]> > > wrote: > > > > > k, it's basically done. > > > if the list is longer than the browser's height, scrolling with both the > > > keyboard > > > and the mouse either feels kinda awkward (because the entire page gets > > > scrolled > > > with .scrollIntoView) or even impossible. > > > what we could do now is the following: > > > put the list in another div with style "overflow:scroll; height: XYpx;" > > > this way scrollIntoView does not affect the entire page. > > > > > > now if anyone can think of better names than "allowEmptyInput" or > > > "showListOnEmptyInput" i will happily use the better suggestions ;) > > > > > > Gerolf > > > > > > > > > On Wed, Apr 23, 2008 at 4:26 PM, Gerolf Seitz <[EMAIL PROTECTED]> > > > wrote: > > > > > > > nah, i think this should be pretty straight forward. > > > > let me take a look. > > > > > > > > Gabriel, can you file a jira issue for that? thanks. > > > > > > > > Gerolf > > > > > > > > > > > > On Wed, Apr 23, 2008 at 4:14 PM, Johan Compagner <[EMAIL PROTECTED] > > > > > > > wrote: > > > > > > > > > I guess this is being done because when nothing is typed there is > > > > > normally > > > > > no list? > > > > > > > > > > Gerolf do you see any problem making this configurable so that it > > does > > > > > show > > > > > always a list if there are values? > > > > > > > > > > johan > > > > > > > > > > > > > > > On Wed, Apr 23, 2008 at 2:53 PM, Gabriel Erzse < > > > > > [EMAIL PROTECTED]> > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > I am using the autocomplete feature of Wicket, and I would like > > the > > > > > user > > > > > > to see the entire list of available values when the input field is > > > > > empty. > > > > > > Then, as he starts typing values in the input field, the list of > > > > > values will > > > > > > narrow down. > > > > > > > > > > > > However I see that when the input field is empty, the popup for > > > > > > autocomplete is not displayed (for example when I press down > > arrow). > > > > > I > > > > > > searched in the wicket code and I saw that in file > > > > > "wicket-autocomplete.js", > > > > > > in function "doUpdateChoices" there are two checks for the > > situation > > > > > when > > > > > > the input field is empty. These checks don't allow for the popup > > to > > > > > be > > > > > > visible. > > > > > > > > > > > > So, my questions would be: does anyone know why this was done so, > > > > > and can > > > > > > I somehow disable this behavior? I would find it really useful to > > be > > > > > able to > > > > > > display a list of values even when the input field is empty. > > > > > > > > > > > > Thank you, > > > > > > Gabi. > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
