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

Hudson commented on AMBARI-19196:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #527 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/527/])
AMBARI-19196. BG operations modal windows are too small to show the 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=22b027efb782cb4b33cc0a487262ad8de9cc097e])
* (edit) ambari-web/app/views/common/modal_popup.js


> BG operations modal windows are too small to show the content (in certain 
> scenarios) [Chrome]
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19196
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19196
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19196.patch, AMBARI-19196_branch-2.5.patch
>
>
> 1. Login to Ambari
> 2. Click on BG operations.
> 3. Click on some action link which have relatively lesser content, e.g Hosts, 
> with only one host link.
> 4. Click on the link to get more details
> 5. Intermittently the details window also have the same dimension of the 
> previous window and as a result the user is not able to view the content
> BG operations modal window should be resizable as intermittently modal 
> windows are too small to view the content[Chrome].
> This behavior is observed when we navigate to the granular details and the 
> previous window was smaller size due to lesser content. Please see the 
> screenshots
>  Intermittently the details window also have the same dimension of the 
> previous window and as a result the user is not able to view the content



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

Reply via email to