Bug 872352 - IE8 capability with new d3 chart solution
Summary: IE8 capability with new d3 chart solution
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Usability
Version: 4.5
Hardware: i686
OS: Windows
unspecified
unspecified
Target Milestone: ---
: RHQ 4.7
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 872347
TreeView+ depends on / blocked
 
Reported: 2012-11-01 20:42 UTC by Mike Thompson
Modified: 2013-09-03 14:44 UTC (History)
1 user (show)

Fixed In Version: RHQ 4.7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-03 14:44:27 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Thompson 2012-11-01 20:42:54 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Mike Thompson 2013-04-19 00:53:16 UTC
Added deferred binding support for ie8 so that IE8 will not render d3 charts (as it is not capable). A message saying that "Charting is not available for this browser." is rendered instead.



<replace-with class="org.rhq.enterprise.gui.coregui.client.inventory.common.charttype.StackedBarMetricGraphIE8Impl">
        <when-type-is class="org.rhq.enterprise.gui.coregui.client.inventory.common.charttype.StackedBarMetricGraphImpl"/>
            <when-property-is name="user.agent" value="ie8"/>
    </replace-with>

This deferred binding is in place for charting now so that other implementations for special browsers or TBD circumstances can easily be added later.

Comment 3 Mike Thompson 2013-04-19 20:17:35 UTC
Also links that point to charts are disabled as well (inventory summary resource measurements link).

master commit id: ab668d8

Comment 4 Heiko W. Rupp 2013-09-03 14:44:27 UTC
Bulk closing of issues in old RHQ releases that are in production for a while now.

Please open a new issue when running into an issue.


Note You need to log in before you can comment on or make changes to this bug.