[
https://issues.apache.org/jira/browse/AMBARI-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279785#comment-15279785
]
Hadoop QA commented on AMBARI-16432:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12803242/AMBARI-16432.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6818//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6818//console
This message is automatically generated.
> Give user visual feedback while we do background request and next button is
> disabled
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-16432
> URL: https://issues.apache.org/jira/browse/AMBARI-16432
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16432.patch
>
>
> User may think that he is blocked or did something wrong, on one of wizard
> (any wiz) steps because Next button can be disabled (on significant time),
> especially on big clusters or in case of slow connection speed, or bad ping.
> We have many places where we disable "Next" button while we do some
> background operations/calculations. Usually this are requests on
> validations/recommendations. Sometimes this can take a significant time
> frame, before we will enable Next button. At the same time user is not aware
> why Next button is disabled and he cannot proceed to next step. We should
> give user a visual feedback that we are doing some calculations and that's
> why Next button is disabled. The easiest way is, to switch Next button on
> spinner while we do our background stuff.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
