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

Ilya Borisov edited comment on IGNITE-10965 at 2/4/19 9:46 AM:
---------------------------------------------------------------

After discussion, [~Klaster_1], [~vabramova], [~ysergeev] and [~kuaw26] decided 
to use slightly different pattern:
1. Disable button after starting potentially long operation.
2. Swap red line under app header with progress-line component to indicate 
running operation.


was (Author: klaster_1):
After discussion, [~Klaster_1], [~vabramova], [~ysergeev] and [~kuaw26] decided 
use slightly different pattern:
1. Disable button after starting potentially long operation.
2. Swap red line under app header with progress-line component to indicate 
running operation.

> Web console: in progress state for buttons
> ------------------------------------------
>
>                 Key: IGNITE-10965
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10965
>             Project: Ignite
>          Issue Type: Improvement
>          Components: wizards
>            Reporter: Ilya Borisov
>            Assignee: Alexander Kalinin
>            Priority: Minor
>         Attachments: !icons.png, DisableBtn.png, ProgressBtn.png
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> *The problem:*
>  Some actions triggered by user might take awhile, during which user can 
> click on action button multiple times and, depending on internal details, 
> cause unwanted side effects (like registering multiple users instead of one).
> *Solution:*
>  Disable action button when action is running. Tell user to wait that 
> something is happening. This can be integrated into special button state.
> Places new button state can be used in:
>  - User registration.
> I'd rather prefer that new button state would:
>  - Not affect button dimensions because sudden button size change might look 
> uncanny. Overlays are OK, though. This probably rules out spinning indicator 
> inline with button label.
>  - Not hide original button label so.user always knows what's in progress.
>  - Work for all button styles. Unique background for each button type is not 
> OK, same background or overlay is OK. This will simplify the implementation.
>  The requirements above are not set in stone, every point is open for 
> discussion.
> [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement.
>  
> Useful article: [https://habr.com/ru/post/271881/]
> Sample implemenation: https://johannesjo.github.io/angular-promise-buttons/
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to