ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Konstantinov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-10965) Web console: in progress state for buttons
Date Thu, 07 Feb 2019 10:29:00 GMT

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

Pavel Konstantinov edited comment on IGNITE-10965 at 2/7/19 10:28 AM:
----------------------------------------------------------------------

Tested:
- sign up
- sign in
- profile\save


was (Author: pkonstantinov):
Tested:
- sign up
- sign in
-profile\save

> 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: Pavel Konstantinov
>            Priority: Minor
>         Attachments: !icons.png, DisableBtn.png, ProgressBtn.png
>
>   Original Estimate: 8h
>          Time Spent: 4h 10m
>  Remaining Estimate: 3h 50m
>
> *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)

Mime
View raw message