Ok, I think I confirmed this as a bug: if I disable the checking using
configuration.add(SymbolConstants.UNKNOWN_COMPONENT_ID_CHECK_ENABLED, "false"); then my use case works ok, so my code is absolutely legit. I have opened JIRA https://issues.apache.org/jira/browse/TAP5-1745 that should be IMHO be corrected before the 5.3 is released OR disable it by default. Otherwise every app will break that uses event bubbling.. Howard: as you implemented the original feature could you comment if this is right? - Ville -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-3-rc3-event-bubbling-bug-tp4966490p4968931.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
