tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2555) Add an okClass parameter to Confirm mixin
Date Fri, 08 Jul 2016 19:22:10 GMT

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

ASF subversion and git services commented on TAP5-2555:
-------------------------------------------------------

Commit 0f4f1f872440a3fa9919e7eaf082b52431b763a3 in tapestry-5's branch refs/heads/master from
kaosko
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=0f4f1f8 ]

TAP5-2555: Add an okClass parameter to Confirm mixin

- apply
https://patch-diff.githubusercontent.com/raw/apache/tapestry-5/pull/5 as
a patch

> 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)

Mime
View raw message