It appears that this fix is already working in 6.11.0-SNAPSHOT.
The fix was committed here:
https://github.com/apache/wicket/commit/bfd4649656f4f51c8d1a164cc14cb5b8dc71f89d
See https://issues.apache.org/jira/browse/WICKET-5315
I applied that change to my code and the auto complete works now.
O
I added this case to JIRA with a quickstart. It is a critical bug for
my company.
https://issues.apache.org/jira/browse/WICKET-5332
Jered
On 08/27/2013 06:39 AM, Sven Meier wrote:
Hi Jan,
autoComplete is a little delicate in the ordering of javascript event
registrations, so this might not
Hi Jan,
autoComplete is a little delicate in the ordering of javascript event
registrations, so this might not have any effects on other components.
A quickstart will help to identify the problem.
Sven
On 08/27/2013 03:21 PM, TechDB wrote:
Hello,
I can confirm the behavior. It happens on a
Hello,
I can confirm the behavior. It happens on al AutoComplete fields that are
added lazy via ajax. The mentioned error in ajax debug "ERROR: Cannot find
element with id: null" is produced by the script that tries to add the
autocomplete event to the element via header contribution. It seems tha
Issue and quickstart please.
Sven
manuelbarzi schrieb:
>sorry, i try to be more specific. after moving to wicket 6.10.0, it fails in
>two different cases:
>
>case 1: when adding this behavior:
>
>autoComplete.add(new AjaxFormComponentUpdatingBehavior("onKeyUp") {
> @Override
> prote
sorry, i try to be more specific. after moving to wicket 6.10.0, it fails in
two different cases:
case 1: when adding this behavior:
autoComplete.add(new AjaxFormComponentUpdatingBehavior("onKeyUp") {
@Override
protected void onUpdate(final AjaxRequestTarget target) {
Wicket example works fine with AutoCompleteTextField. Can you open an
issue with your quickstart project?
> does anybody experience the same?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands,
AutoCompletePage in wicket-examples works fine here.
Sven
On 08/27/2013 10:27 AM, manuelbarzi wrote:
hi,
after moving from wicket 6.9.1 to 6.10.0 caused all AutoCompleteTextFields
to break up in the application (no results shown). also a quick test created
from scratch with this component does
