[
https://issues.apache.org/jira/browse/AMBARI-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529069#comment-14529069
]
Hudson commented on AMBARI-10937:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2518 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2518/])
AMBARI-10937. Filtering configs should not hide tabs. Instead should disable
selection. (onechiporenko) (onechiporenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=172dd8cf4c3e944a1d42d90f39108b2ad7ac22b6)
* ambari-web/app/templates/common/configs/service_config_wizard.hbs
* ambari-web/app/views/common/configs/service_config_view.js
* ambari-web/app/templates/common/configs/service_config.hbs
* ambari-web/app/views/common/configs/service_config_container_view.js
> Filtering configs should not hide tabs. Instead should disable selection.
> -------------------------------------------------------------------------
>
> Key: AMBARI-10937
> URL: https://issues.apache.org/jira/browse/AMBARI-10937
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-10937.patch
>
>
> When filtering (typing text in filter or selecting filter-dropdowns), we
> currently hide tabs which do not have any matches. Instead of hiding these
> tabs, we should disable the selection of tabs so that their content cannot be
> shown.
> If I am in TabA and matches happen in TabB and TabC, then we should
> automatically switch to next enabled tab (TabB), and show+disable selecting
> TabA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
