Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 8 Sep 2014 12:02:28 +0000 (UTC)
From: "Andrii Tkach (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12739860.1410177629000.16354.1410177748415@Atlassian.JIRA>
In-Reply-To: <JIRA.12739860.1410177629000@Atlassian.JIRA>
References: <JIRA.12739860.1410177629000@Atlassian.JIRA>
 <JIRA.12739860.1410177629563@arcas>
Subject: [jira] [Updated] (AMBARI-7196) Config history table pagination
 strange behavior
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrii Tkach updated AMBARI-7196:
---------------------------------
    Attachment: AMBARI-7196.patch

> Config history table pagination strange behavior
> ------------------------------------------------
>
>                 Key: AMBARI-7196
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7196
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7196.patch
>
>
> Navigate to Dashboard->Config History.
> Check items per page is set to 10.
> Also need to have more then 10 table items to have second page.
> navigate to second page using 'next page' button (blue right arrow)
> Then navigate somewhere from config history page (For example navigate to ZooKeeper service page).
> Again navigate to Dashboard->Config History.
> Table shows first page with 10 items.
> Wait for 10 seconds. 
> Page itself switches to second page.
> Probably this is wrong, table should show first page, not page last viewed. 
> Or it should immediately navigate to last viewed page, not after 10 seconds delay.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)