You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Hendy Irawan (JIRA)" <ji...@apache.org> on 2013/11/08 06:34:18 UTC

[jira] [Commented] (WICKET-5360) Add "auto-disabling on submit" Button and Link components

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

Hendy Irawan commented on WICKET-5360:
--------------------------------------

Thanks [~svenmeier], I'll try proposing to WicketStuff then.

> Add "auto-disabling on submit" Button and Link components
> ---------------------------------------------------------
>
>                 Key: WICKET-5360
>                 URL: https://issues.apache.org/jira/browse/WICKET-5360
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.8.0
>            Reporter: Hendy Irawan
>         Attachments: AutoDisableAjaxButton.java, AutoDisableAjaxCallListener.java
>
>
> A lot of people (from mailing list, StackOverflow, etc.) are asking for how to do a very common UI pattern: disable the button/link during submission or AJAX request, and re-enable it otherwise.
> Many then resort to various hacks which may be fragile. Have these components in Wicket core will make it much easier to implement this very common pattern.
> Here I provide our implementation of the auto-disabling components (attached files), taken from https://github.com/soluvas/soluvas-web project.



--
This message was sent by Atlassian JIRA
(v6.1#6144)