An issue with the Resource and ResourceGroup metric D3 portlets caused chart data that exceeded the boundaries of the portlet to be cut off. There was no way to resize the view to see all the data on the dashboard. The portlet had to be resized manually so all data could be viewed. A fix implemented for the Resource and ResourceGroup metric D3 portlets now sets a fixed width for the graph container div, and provides horizontal scroll-bars when required.
Description of problem:
If you have a metric chart on your dashboard that goes beyond the window size, no horizontal scrollbars are created, so the only way to see the rest of your chart is to resize that window
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new Dashboard
2. Add a new portlet for a Resource Metric Chart, i.e. Platform resource > Used Memory, notice the wide of the chart.
3. Now add a column, in the new column add another portlet for Resource Metric Chart. I attached a screenshot to demonstrate.
You will not have a horizontal scrollbar, so you can scroll to see the rest of your charts.
Created attachment 882814 [details]
screenshot to show missing scrollbar
Assigning to Libor as this might be UI/patternfly related.
Not related to patternfly, issue was present in 3.2.0 and remains in 3.3.0 however it should be easy to fix.
time: 2014-09-23 13:24:37 +0200
author: Libor Zoubek - email@example.com
message: Bug 1084586 - Horizontal scrollbars are missing from Dashboard
Resource and ResourceGroup metric D3 portlets now set fixed
width for graph container div and allow horizontal scrollbars
Cherry-picked over to release/jon3.3.x
Author: Libor Zoubek <firstname.lastname@example.org>
Date: Tue Sep 23 13:20:46 2014 +0200
Bug 1084586 - Horizontal scrollbars are missing from Dashboard
Resource and ResourceGroup metric D3 portlets now set fixed width for graph
container div and allow horizontal scrollbars to appear.
(cherry picked from commit aade12c500a1ae648ebcc163913fd0d1bf8b5950)
Signed-off-by: Thomas Segismont <email@example.com>
Moving to ON_QA as available for test with build: