You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "I D (JIRA)" <ji...@apache.org> on 2016/06/29 10:17:37 UTC

[jira] [Commented] (TAP5-2555) Add an okClass parameter to Confirm mixin

    [ https://issues.apache.org/jira/browse/TAP5-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354985#comment-15354985 ] 

I D commented on TAP5-2555:
---------------------------

Patch submitted: https://github.com/apache/tapestry-5/pull/5

> 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
>            Priority: Minor
>
> 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)