Hi Martin,

the suggested solution needs AjaxRequestAttributes in order to display the 
confirm dialog. In an non Ajax setting there would be no ajaxrequest though.

Best regards

marcel

> Am 27.05.13 um 11:37 schrieb Martin Grigorov
>
> > Hi Marcel,
> >
> >
> >
> > What exactly is the issue with non-Ajax links ?
> >
> >
> >
> >
> >
> > On Mon, May 27, 2013 at 12:34 PM, Marcel Hoerr <[email protected]> wrote:
> >
> >
> >
> > > Hi wicket community,
> >
> > >
> >
> > > i have a question about how to implement a confirm dialog via javascript
> >
> > > on a button or link. Before wicket 6 we used a simple behavior (as
> >
> > > mentioned here:
> >
> > > https://cwiki.apache.org/WICKET/getting-user-confirmation.html) which
> >
> > > could be used to enrich any button or link (ajaxified or not) at any time.
> >
> > > With wicket 6 this solution is not working anymore.The suggested
> >
> > > (javascript) solution on
> >
> > > https://cwiki.apache.org/WICKET/getting-user-confirmation.html[https://cwiki.apache.org/WICKET/getting-user-confirmation.html]has
> > >  two downsides (from my perspective):
> >
> > >
> >
> > > - It requires an ajax component (button or link).
> >
> > > - It extends a component. As we use different basic components (which use
> >
> > > buttons or links – not always their ajax companions), we would have to
> >
> > > extends all these basic components to be able use a confirm dialog on them
> >
> > > for certain use cases.
> >
> > >
> >
> > > Are there any other suggestions out there or is the suggested solution
> >
> > > mentioned above the new “wicket way” to achieve a confirm dialog?
> >
> > >
> >
> > > Best regards
> >
> > >
> >
> > > marcel
> >
> > >
> >
> > > ---------------------------------------------------------------------
> >
> > > To unsubscribe, e-mail: [email protected]
> >
> > > For additional commands, e-mail: [email protected]
> >
> > >
> >
> > >

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to