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

["Sven Meier (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sven Meier resolved WICKET-5360.
--------------------------------

    Resolution: Won't Fix

The proposed solution is too specific to be added to Wicket.

How to handle UI blocking during Ajax requests (showing a veil, disabling buttons, global or on a component basis) has to be handled individually in each application.

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