On Thu, Oct 28, 2021 at 1:26 PM Nathan Quirynen
wrote:
> Thank you for your reply.
>
My pleasure to (at least try to) help!
> Are you sure this should work as I thought it would? I just cannot get
> it to work even in a simple case.
>
I've given some more thought to it and I discovered I was
Thank you for your reply.
I have just made a simple test case in my testing Tapestry project to
avoid other possible handlers as you suggested could exist:
A page class which contains a component that triggers an event using
componentResources and the page class uses t:type="layout".
But agai
Hello!
Events do bubble up in the component hierarchy/tree until they're handled,
so the situation is a bit weird. Have you checked whether there's some
other component in between which is catching this event and thereby
avoiding Layout from receiving it?
On Wed, Oct 27, 2021 at 3:38 PM Nathan Qu
Hi,
I want to bubble up an event from a component, which is deeply nested in
other components, to an outer component, but it only bubbles up to the
page and not further to the component defined as t:type="***" in the page.
Some simplified example code to clarify:
Page:
...
..
