Kendo window adds up in DOM

[Bergmann Manfred <mb...@software-by-mabe.com>]

Hi.

I have the following problem.
We have a Kendo `Window` which we use as confirmation window with form and checkbox.
After the first successful submit (checkbox verification OK) of the window form any new spawned window submits ‚value=on‘ even though the checkbox is not ‚checked‘.

The window is part of an inner container that is part of an outer container.
The outer container creates new inner containers depending on a navigation.
So basically a new window is created each time for the same WicketId.

What appears to happen is that whenever an inner container is created that contains a window, a new window is added in the DOM, under body.
Any previous window is not removed.

I have tried to create a stripped down version of this in a simple page but can’t reproduce the issue there.
In this stipped down version the windows are removed from DOM.

I’m assuming (couldn’t really verify this yet) that after a successful submit (checkbox checked) some listeners are not completely cleaned up and a new window uses some old data, or the OK button of the new Window actually triggers a listener of some old window which contained the checked checkbox, hence the ‚value=on‘ is transmitted.

After a browser ‚refresh‘ this behavior is gone and a new window works properly, once.


Anyone has an idea about what happens here?



Regards,
Manfred


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Kendo window adds up in DOM

[Sebastien Briquet <sb...@apache.org>]

Hi Manfred,

Are you using a FormWindow? Because it is designed to prevent this behavior.
https://github.com/sebfz1/wicket-jquery-ui/blob/wicket8.x/wicket-kendo-ui/src/main/java/com/googlecode/wicket/kendo/ui/widget/window/FormWindow.java#L192

Otherwise please create a quickstart so I can have a better look...

Thanks in advance,
Sebastien.

On Mon, May 20, 2019 at 4:13 PM Bergmann Manfred <mb...@software-by-mabe.com>
wrote:

> Hi.
>
> I have the following problem.
> We have a Kendo `Window` which we use as confirmation window with form and
> checkbox.
> After the first successful submit (checkbox verification OK) of the window
> form any new spawned window submits ‚value=on‘ even though the checkbox is
> not ‚checked‘.
>
> The window is part of an inner container that is part of an outer
> container.
> The outer container creates new inner containers depending on a navigation.
> So basically a new window is created each time for the same WicketId.
>
> What appears to happen is that whenever an inner container is created that
> contains a window, a new window is added in the DOM, under body.
> Any previous window is not removed.
>
> I have tried to create a stripped down version of this in a simple page
> but can’t reproduce the issue there.
> In this stipped down version the windows are removed from DOM.
>
> I’m assuming (couldn’t really verify this yet) that after a successful
> submit (checkbox checked) some listeners are not completely cleaned up and
> a new window uses some old data, or the OK button of the new Window
> actually triggers a listener of some old window which contained the checked
> checkbox, hence the ‚value=on‘ is transmitted.
>
> After a browser ‚refresh‘ this behavior is gone and a new window works
> properly, once.
>
>
> Anyone has an idea about what happens here?
>
>
>
> Regards,
> Manfred
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>