seems like an good idea.. And may also help events overflowing.. Like what happened in the wicket reaction game..
As for the boolean suggested somewhere in the thread, I guess as aways let the default be the best practice as you've suggested. regards Nino 2010/8/17 Martijn Dashorst <[email protected]> > Currently we don't stop events from bubbling after an Ajax call. This > can be harmful in the following case: > > <tr onclick="... link for going to details of this record..."> > <td><input type="checkbox" onclick="ajax call for AjaxCheckBox" /> </td> > </tr> > > If a user clicks on the checkbox, we send in an ajax request for > selecting the element. But after the ajax call the onclick bubbles up > to the tr (as browsers do) and navigates to the details. > > I think that we should always cancel the event after the ajax request > was handled to prevent it from bubbling up. Does anybody disagree? > > (Note that the CancelEventIfNoAjaxDecorator is a partial solution in > that it only prevents the default action from happening, not the > bubbling part (at least for checkbox). > > Martijn > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >
