Hi,
I thought we already moved the old implementation to wicket-stuff, but
apparently I forgot to do it actually.
For explanation: the old ModalWindow is riddled with JS and dynamically
generated HTML markup which we didn't want to maintain any more.
Sven
On 20.10.23 11:22, Korbinian Bachl wrote:
Hi,
just a short question. Since wicket 10 removed ModalWindow and insists now on
using ModalDialog even so many features of ModalWindow aren't in ModalDialog
existing
(for example closeCallback, resize, move, header, closebutton, init of width,
height etc.etc).
Would it maybe possible if the removal of ModalWindow gets postponed to wicket
11?
Problem is one can't use wicket 9 with jakarta (last lib that holds us back)
and we have the ModalWindows over so many places with usages that arent really
existing in ModalDialog anymore.
(Or maybe a ModalWindow from WicketStuff?)
Best,
KB
