Hi Sven and Andrea! I'd suggest pure CSS popup handled by wicket ajax. Maybe very simple js to add some class to the body (for example to add a blur).
``` <div id="popup" class="open"> <i class="icon-window-close" id="popup__close"></i> <div class="popup__outer"> <div id="popup__content"> <div>My beautiful popup content</div> </div> </div> </div> ``` ``` body.has-popup { overflow: hidden; } body.has-popup>.container { filter: blur(5px); overflow: hidden; } #popup { overflow-y: auto; } #popup__close { display: none; } #popup__content { max-width: 700px; margin: 0 auto; background: #222222AA; padding: 10px; } #popup.open { position: fixed; width: 100vw; height: 100vh; left: 0; top: 0; } #popup.open .popup__outer { display: flex; justify-content: center; flex-direction: column; min-height: 100%; margin-bottom: 50px; /* fix issue with chrome control bar */ } #popup.open #popup__close { position: fixed; top: 20px; right: 20px; font-size: 200%; display: block; } #popup.open #popup__close:before { text-shadow: 0 0 10px grey; } *```* чт, 21 нояб. 2019 г. в 04:41, Sven Meier <s...@meiers.net>: > Hi Andrea, > > sorry my mistake, the most recent issue on this topic is: > > https://issues.apache.org/jira/browse/WICKET-6666 > > And there are two branches actually with Igor's (WICKET-6666_modal-dialog) > and my (WICKET-6666_modal-dialog-2) proposal respectively. > > IMHO we should try to find a very simple solution for the common middle > ground that > - supports more than just alert dialogs, e.g. forms > - doesn't impose huge markup on users > - doesn't need much if configuration > - isn't a one-fits-all component (we'll fail with that anyway) > - is Wicket-y, e.g server rendered, no JS required and simple > > Have fun > Sven > > > > Am 20. November 2019 15:48:24 MEZ schrieb Andrea Del Bene < > an.delb...@gmail.com>: > >To be clear, changes for WICKET-3404 are on branch > >'WICKET-6666_modal-dialog-2'? > > > >On Tue, Nov 19, 2019 at 9:13 PM Andrea Del Bene <an.delb...@gmail.com> > >wrote: > > > >> Thank you ! > >> > >> On Tue, Nov 19, 2019, 8:58 PM Andrew Kondratev <and...@kondratev.pro> > >> wrote: > >> > >>> Hi! > >>> > >>> Please let me know if you need further assistance with WICKET-6703 > >>> <https://issues.apache.org/jira/browse/WICKET-6703> or WICKET-3404 > >>> <https://issues.apache.org/jira/browse/WICKET-3404> > >>> > >>> Cheers, > >>> Andrew > >>> > >>> ср, 20 нояб. 2019 г. в 06:49, Sven Meier <s...@meiers.net>: > >>> > >>> > Hi Andrea, > >>> > > >>> > both issues are ready. > >>> > > >>> > Andrew and I have put a lot of effort into WICKET-6703, which IMHO > >is a > >>> > really nice improvement for Wicket 9. > >>> > > >>> > Have fun > >>> > Sven > >>> > > >>> > > >>> > On 19.11.19 12:10, Andrea Del Bene wrote: > >>> > > Personally I'd rather target both issues for Wicket 9. It's my > >>> > > understanding that WICKET-6703 > >>> > > <https://issues.apache.org/jira/browse/WICKET-6703> is nearly > >>> > completed, so > >>> > > we might consider to merge its feature branch. Correct me if I'm > >>> wrong. > >>> > > > >>> > > On Thu, Nov 14, 2019 at 6:06 PM Sven Meier <s...@meiers.net> > >wrote: > >>> > > > >>> > >> Hi Andrea, > >>> > >> > >>> > >> IMHO we should decide WICKET-6703 "eval" first: > >>> > >> > >>> > >> https://issues.apache.org/jira/browse/WICKET-6703 > >>> > >> > >>> > >> Either we stop that endeavour or it has to go into Wicket 9. > >>> > >> > >>> > >> Personally I'd like to have progress on WICKET-3404 "modal > >window" > >>> too: > >>> > >> > >>> > >> https://issues.apache.org/jira/browse/WICKET-3404 > >>> > >> > >>> > >> Have fun > >>> > >> Sven > >>> > >> > >>> > >> > >>> > >> On 14.11.19 10:07, Andrea Del Bene wrote: > >>> > >>> WDYT? :-) > >>> > >>> > >>> > > > >>> > > >>> > >> > > > >-- > >Andrea Del Bene. > >Apache Wicket committer. >