Martin. Thanks for explanation. This little thing was preventing me from jumping to wicket 7. Now I can migrate my project :-)
On Mon, May 9, 2016 at 4:17 PM, Martin Grigorov <[email protected]> wrote: > On Mon, May 9, 2016 at 4:14 PM, Ernesto Reinaldo Barreiro < > [email protected]> wrote: > > > Problem was > > > > > attributes.setEventPropagation(AjaxRequestAttributes.EventPropagation.STOP > > ); > > > > was need. Before STOP was the default, now it is BUBBLE. Just wondering > > why default was changed? > > > It changed because BUBBLE is the default in the browser DOM. > > > > > > On Mon, May 9, 2016 at 3:26 PM, Ernesto Reinaldo Barreiro < > > [email protected]> wrote: > > > >> This seem to be some bug on the bootstrap layer NOT a Wicket bug: > >> stripping bootstrap specifics makes wicket AJAX work. > >> > >> On Mon, May 9, 2016 at 3:02 PM, Ernesto Reinaldo Barreiro < > >> [email protected]> wrote: > >> > >>> @Martin, > >>> > >>> cleaned up working branch. > >>> > >>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/604 > >>> > >>> On Mon, May 9, 2016 at 1:40 PM, Ernesto Reinaldo Barreiro < > >>> [email protected]> wrote: > >>> > >>>> Hi, > >>>> > >>>> Sorry for the long time it took... Today I finally managed to find > some > >>>> free time to create something you can use to see the problem in > action: > >>>> > >>>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/603 > >>>> > >>>> Shows a component (Bootstrap radio choice) that does not work in > wicket > >>>> 7.3.0 > >>>> > >>>> and PR > >>>> > >>>> https://github.com/l0rdn1kk0n/wicket-bootstrap/pull/602 > >>>> > >>>> shows the same component working on 6.3. > >>>> > >>>> [image: Inline image 1] > >>>> > >>>> @Martin, > >>>> > >>>> I will later on create a new (cleaner) PR to replace 603 to add only > >>>> radio choice renderer for 6.x. > >>>> > >>>> Disclaimer: I do not know if this is an error introduced by the > >>>> bootstrap layer or if this can be reproduced with a bare bones wicket > >>>> example. > >>>> > >>>> > >>>> On Wed, Nov 18, 2015 at 2:00 PM, Ernesto Reinaldo Barreiro < > >>>> [email protected]> wrote: > >>>> > >>>>> Let me see is I find the time to created it (it uses my own bootstrap > >>>>> components) > >>>>> > >>>>> On Wed, Nov 18, 2015 at 1:53 PM, Sven Meier <[email protected]> wrote: > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> with a quickstart it would be easy to spot the problem. > >>>>>> > >>>>>> Regards > >>>>>> Sven > >>>>>> > >>>>>> > >>>>>> On 18.11.2015 13:46, Ernesto Reinaldo Barreiro wrote: > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> > >>>>>>> If I "revert" to 6.21.0 problem disappears so this seems to be a > >>>>>>> 7.1.0 > >>>>>>> "issue". > >>>>>>> > >>>>>>> On Tue, Nov 17, 2015 at 9:36 PM, Ernesto Reinaldo Barreiro < > >>>>>>> [email protected]> wrote: > >>>>>>> > >>>>>>> Well it is the same in the sense that no client side AJAX event > >>>>>>>> seems to > >>>>>>>> be triggered. > >>>>>>>> > >>>>>>>> On Tue, Nov 17, 2015 at 9:24 PM, Ernesto Reinaldo Barreiro < > >>>>>>>> [email protected]> wrote: > >>>>>>>> > >>>>>>>> Hi Sven, > >>>>>>>>> > >>>>>>>>> Thanks for the feedback. It should not be the case > >>>>>>>>> > >>>>>>>>> radioGroup = new RadioGroup<T>("radioGroup", getModel()); > >>>>>>>>> tuneRadioGroup(radioGroup); > >>>>>>>>> radioGroup.setRenderBodyOnly(false); > >>>>>>>>> radioGroup.setOutputMarkupId(true); > >>>>>>>>> add(radioGroup); > >>>>>>>>> if(changeHandler != null) { > >>>>>>>>> radioGroup.add(new > >>>>>>>>> AjaxFormChoiceComponentUpdatingBehavior() { > >>>>>>>>> > >>>>>>>>> @Override > >>>>>>>>> protected void onUpdate(AjaxRequestTarget > target) > >>>>>>>>> { > >>>>>>>>> changeHandler.onSelectionChanged(target, > >>>>>>>>> radioGroup.getModel().getObject()); > >>>>>>>>> } > >>>>>>>>> }); > >>>>>>>>> } > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Tue, Nov 17, 2015 at 7:11 PM, Sven Meier <[email protected]> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>>> > >>>>>>>>>> nothing specific I can think of ... perhaps WICKET-5476? > >>>>>>>>>> > >>>>>>>>>> Regards > >>>>>>>>>> Sven > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On 17.11.2015 18:55, Ernesto Reinaldo Barreiro wrote: > >>>>>>>>>> > >>>>>>>>>> Hi, > >>>>>>>>>>> > >>>>>>>>>>> I have a bootstrap based component that uses a RadioGroup > >>>>>>>>>>> + AjaxFormChoiceComponentUpdatingBehavior. This was working > >>>>>>>>>>> perfectly > >>>>>>>>>>> fine > >>>>>>>>>>> on wicket 6. Now is no loger working with wicket 7. Are there > any > >>>>>>>>>>> (obvious) > >>>>>>>>>>> changes on the way RadioGroup works that might be preventing it > >>>>>>>>>>> from > >>>>>>>>>>> working? > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > --------------------------------------------------------------------- > >>>>>>>>>> To unsubscribe, e-mail: [email protected] > >>>>>>>>>> For additional commands, e-mail: [email protected] > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> Regards - Ernesto Reinaldo Barreiro > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> Regards - Ernesto Reinaldo Barreiro > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > --------------------------------------------------------------------- > >>>>>> To unsubscribe, e-mail: [email protected] > >>>>>> For additional commands, e-mail: [email protected] > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Regards - Ernesto Reinaldo Barreiro > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> Regards - Ernesto Reinaldo Barreiro > >>>> > >>> > >>> > >>> > >>> -- > >>> Regards - Ernesto Reinaldo Barreiro > >>> > >> > >> > >> > >> -- > >> Regards - Ernesto Reinaldo Barreiro > >> > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
