Closed VaclavC closed 6 years ago
Hi, yes this is because in several widgets there is a difference between the original html and the rendered/transformed one. In other words, that's when there is a difference between the element
and the wrapper
. https://docs.telerik.com/kendo-ui/api/javascript/ui/widget
The purpose of the default MultiSelect is to be static. In order to get the dynamic part, you will preferably use the lazy version (com.googlecode.wicket.kendo.ui.form.multiselect.lazy.MultiSelect<T>
) and use #refresh(AjaxRequestTarget target)
to reload the data-model.
I'll try it in that way. Thank you for clarification.
Hello,
I'am trying to change MultiSelect with Ajax calls. Relevant part of code:
It updates the select content fine, but with each ajax call a new "nested" select is created on pages. It ends up with something likes this:
This example is after two ajax calls.
If I try to replace whole panel containing MultiSelect instead of onloy changing model, it works at first glance, but after inspection I realized, that similar orphan nodes are created in document tree....
Where may be the problem?