You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by TechDB <te...@gmx.de> on 2013/09/29 02:24:57 UTC
Problems with Autocomplete in 6.11.0
Using 6.11.0 I did realize the following to problems in AutoComplete related
to the JavaScript:
- Indicator gets not deactivated in case of MinimumLength
function actualUpdateChoices() {
showIndicator();
the indicator is activated but in the case that the pre function is not met,
it will never be deavtivated
- the position of the "dropdown" is totally of
in function getPosition(obj) {
var rectangle = obj.getBoundingClientRect();
var leftPosition = rectangle.left || 0;
var topPosition = rectangle.top || 0;
...
obj = obj.offsetParent;
while (obj && obj !== document.documentElement && obj !==
document.body) {
topPosition += obj.offsetTop || 0;
==> the positions are now evaluated using getBoundingClientRect but there is
still a loop to add to this positions using the parent offsets.
Im quite sure that the deactivation of the indicator was just forgotten, but
with the offset thing I am not sure if it allways will deliver wrong
results. At least for all autocomplete we use in our applications we have to
remove the offsetpart
Greetings Jan
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Autocomplete-in-6-11-0-tp4661600.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Problems with Autocomplete in 6.11.0
Posted by Andrea Del Bene <an...@gmail.com>.
Thank you for your feedbacks, I'm working on a patch!
> followed your patch, Jan, but the indicator was not hiding when deleting the
> input value (backspace key). so forced to hide the indicator on auto
> complete hiding [1]. for the moment it works, until the issue is solved in
> the original component.
>
> [1] wicket-autocomplete.js
>
> function hideAutoComplete(){
> ...
> hideIndicator();
> }
>
>
>
>
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Autocomplete-in-6-11-0-tp4661600p4661675.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Problems with Autocomplete in 6.11.0
Posted by manuelbarzi <ma...@GMAIL.COM>.
followed your patch, Jan, but the indicator was not hiding when deleting the
input value (backspace key). so forced to hide the indicator on auto
complete hiding [1]. for the moment it works, until the issue is solved in
the original component.
[1] wicket-autocomplete.js
function hideAutoComplete(){
...
hideIndicator();
}
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Autocomplete-in-6-11-0-tp4661600p4661675.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Problems with Autocomplete in 6.11.0
Posted by TechDB <te...@gmx.de>.
Done:
WICKET-5382
Greetings Jan
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Autocomplete-in-6-11-0-tp4661600p4661637.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Problems with Autocomplete in 6.11.0
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
Please file a ticket.
A quickstart will help to fix it faster.
Thanks!
On Sun, Sep 29, 2013 at 2:24 AM, TechDB <te...@gmx.de> wrote:
> Using 6.11.0 I did realize the following to problems in AutoComplete
> related
> to the JavaScript:
>
> - Indicator gets not deactivated in case of MinimumLength
>
> function actualUpdateChoices() {
> showIndicator();
> the indicator is activated but in the case that the pre function is not
> met,
> it will never be deavtivated
>
>
>
> - the position of the "dropdown" is totally of
>
> in function getPosition(obj) {
> var rectangle = obj.getBoundingClientRect();
> var leftPosition = rectangle.left || 0;
> var topPosition = rectangle.top || 0;
> ...
> obj = obj.offsetParent;
> while (obj && obj !== document.documentElement && obj !==
> document.body) {
> topPosition += obj.offsetTop || 0;
>
> ==> the positions are now evaluated using getBoundingClientRect but there
> is
> still a loop to add to this positions using the parent offsets.
>
>
>
> Im quite sure that the deactivation of the indicator was just forgotten,
> but
> with the offset thing I am not sure if it allways will deliver wrong
> results. At least for all autocomplete we use in our applications we have
> to
> remove the offsetpart
>
>
> Greetings Jan
>
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Problems-with-Autocomplete-in-6-11-0-tp4661600.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>