>> https://github.com/ivaynberg/wicket/tree/component-queuing > > Sorry, I was thinking for some reason that the depth-first search > through the current component's hierarchy would actually traverse into > subcomponent's markup, but I don't think it will. It will stay within > the current component's markup looking for the matching id. Could > fragments screw this up, since their markup is actually contained > within the markup of their parent container?
When fragments are added they materialize as natural markup at the junction point? ** Martin > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
