Re: autocomplete: no popup when field is empty
I am still having issues with this. I am using 1.4-m2 with your newest additions. It is much better but it really only half way gives the user what he is asking for. He wants to list to show up on an empty input. The way you have it implemented is the user has to click on the textfield and then press the down key to get the entire list to show up on an empty input. While this sort of fixes the issue I think it would be more useful if you simply had the list show up when the textfield loads instead of having to click on the textfield and press the down arrow. This will knock down a lot of user confusion. Is there a way to simply always show the div that holds the list of values? I may be confused here but I have not found a way to fix this issue on my own. Thanks T Gerolf Seitz wrote: right, but since it's in extensions, everything has to be homegrown :/ On Wed, Apr 23, 2008 at 11:11 PM, Johan Compagner [EMAIL PROTECTED] wrote: not by us ;) Gerolf is ofcourse using a standard fully tested lib right ;) On Wed, Apr 23, 2008 at 10:58 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: 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/ 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
Re: autocomplete: no popup when field is empty
has this been implemented yet? I just posted a similar question to this and I would like to show the list of choices even if the textfield is blank as well. Thanks T Johan Compagner wrote: showListOnEmptyInput looks descriptive enough for me :) 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] -- View this message in context: http://www.nabble.com/autocomplete%3A-no-popup-when-field-is-empty-tp16855424p17497544.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: autocomplete: no popup when field is empty
right, but since it's in extensions, everything has to be homegrown :/ On Wed, Apr 23, 2008 at 11:11 PM, Johan Compagner [EMAIL PROTECTED] wrote: not by us ;) Gerolf is ofcourse using a standard fully tested lib right ;) On Wed, Apr 23, 2008 at 10:58 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: 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/ 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]
autocomplete: no popup when field is empty
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]
Re: autocomplete: no popup when field is empty
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]
Re: autocomplete: no popup when field is empty
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]
Re: autocomplete: no popup when field is empty
Done: https://issues.apache.org/jira/browse/WICKET-1562 Thanks, Gabi. - Original Message From: Gerolf Seitz [EMAIL PROTECTED] To: users@wicket.apache.org Sent: Wednesday, April 23, 2008 5:26:13 PM Subject: Re: autocomplete: no popup when field is empty 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]
Re: autocomplete: no popup when field is empty
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]
Re: autocomplete: no popup when field is empty
showListOnEmptyInput looks descriptive enough for me :) 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]
Re: autocomplete: no popup when field is empty
i _could_ use something from a combobox i did some time ago: http://people.apache.org/~gseitz/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]
Re: autocomplete: no popup when field is empty
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]
Re: autocomplete: no popup when field is empty
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]
Re: autocomplete: no popup when field is empty
not by us ;) Gerolf is ofcourse using a standard fully tested lib right ;) On Wed, Apr 23, 2008 at 10:58 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: 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/ 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]
