[
https://issues.apache.org/jira/browse/TAP5-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kalle Korhonen resolved TAP5-2555.
----------------------------------
Resolution: Fixed
Assignee: Kalle Korhonen
Fix Version/s: 5.5.0
Applied without changes, thanks!
> Add an okClass parameter to Confirm mixin
> -----------------------------------------
>
> Key: TAP5-2555
> URL: https://issues.apache.org/jira/browse/TAP5-2555
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.4.1
> Reporter: I D
> Assignee: Kalle Korhonen
> Priority: Minor
> Fix For: 5.5.0
>
>
> The confirm-click script module references an option named "okClass" and
> renders it as the class of the ok button in the dialog. This can be very
> useful, in case we want to later attach a js listener to the click of this
> button (without this there is no way to create a css selector that uniquely
> identifies the ok button of a specific "Confirm" dialog).
> However, it seems as though on the server side code, someone forgot to take
> this value as a parameter, and then pass it along to the client-side
> runDialog function.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
