Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.1.3
-
None
Description
In a simple component (@Selector) that has a PropertySelection (named data) and this:
@EventListener(targets="data", events="onchange")
public void doSelect()
and in a page that includes this let's say 3 times:
<form jwcid="@Form">
<span jwcid="@Selector"/>
<span jwcid="@Selector"/>
<span jwcid="@Selector"/>
</form>
Only the first selector triggers its listener + i dont see javascript that would bind the onchange event of the other ones.
Is this something trivial to fix?
Is this a known limitation of the EventListener annotation?
Would an EventListener component make things easier in such cases?
(btw, TAPESTRY-2070 could be similar)
Attachments
Attachments
Issue Links
- is duplicated by
-
TAPESTRY-2070 EventListener on checkbox components within a @For loop - Issues
- Resolved
- relates to
-
TAPESTRY-2250 EventListener in components that get included in a page within a loop are triggered incorrectly
- Open