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

Mona Chitnis updated OOZIE-1892:
--------------------------------

    Attachment: window_without_scroller.JPG
                window_without_body.JPG

Attaching some screenshots

!window_without_body!
!window_without_scroller!

> Oozie web-console WF actions window should be auto-size and not fixed size
> --------------------------------------------------------------------------
>
>                 Key: OOZIE-1892
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1892
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk, 4.0.1
>            Reporter: Mona Chitnis
>             Fix For: trunk
>
>         Attachments: window_without_body.JPG, window_without_scroller.JPG
>
>
> A user reported the following:
> facing some issue with oozie web console UI
> 1. If I click on a pig action it opens a window with no body
> 2. If a coordinator has more than 15 instances invoked there is no scroller to
> see the below 15th row - had to resize the window (very non-intuitive) to get 
> the scroller bar
> facing same issue on two browsers chrome and firefox.
> 3. Weird that the window also does not have a horizontal scrollbar.  My mouse
> supports horizontal scrolling and even with that I can't scroll right enough 
> to
> see the vertical scrollbar.
> Some suggestion from another UI developer (Kendall Thrapp):
> The problems are largely due to the static height and width applied to some of
> the divs wrapping the whole table.  Playing around in Chrome's developer tools
> I was able to get the scrollbars working correctly by:
>  - remove fixed width from div with class x-panel
>  - remove fixed height and width from div with class x-panel-body
>  - remove fixed height and width from div with class x-grid3
>  - remove fixed width from div with class x-grid3-scroller
> We can fix the oozie-console.js to incorporate either the above suggestions 
> or others.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to