Ticket #1454 (closed defect: fixed)

Opened 10 months ago

Last modified 8 months ago

Clicked button should (perhaps optionally) be disabled until response received

Reported by: Marc Englund Owned by: Joonas Lehtinen
Priority: minor Milestone:
Component: undefined Version:
Keywords: Cc:
Known Issue description:
Hours estimate: Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: yes Contract:

Description

Example 1: Button starts search that takes from a few seconds to 1 minute to complete; clicking button again during search should not be possible. Thread + progressbar to complicated in basic situations. Example 2: dad tends to double-click everything.

This might be an issue with some other components, but button is surely most important. We could block the whole client while processing request, but this is always a good idea. The basic use-cases could be solved by disabling clicked button until response received.

Suggested solution: Disable button after click until response received (switch-mode should probably not do this), change cursor to 'wait' (hourglass).

Change History

Changed 10 months ago by Marc Englund

  • milestone changed from User Interface Library 5.1.2 to User Interface Library 5.2 enhancement candidates

Changed 8 months ago by Matti Tahvonen

  • priority changed from undefined to minor
  • milestone deleted

will not fit into 5.2

Maybe a totally new component. BlockingButton? which disables all actions on window until a proper responce from server.

Changed 8 months ago by Joonas Lehtinen

  • status changed from new to closed
  • resolution set to fixed

IMO the recent changes to event processing (queuing on client and more sent after XHR returns) make this mostly unnecessary.

Please reopen if there is still need for this!

Note: See TracTickets for help on using tickets.