tracker issue : CF-3816026

select a category, or use search below
(searches all categories and all time range)
Title:

CFCHART : showLegend property when specified in cfchart tag does not override the property defined in style file

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): / ext-user (Anuj Nawani)

Created: 09/01/2014

Components: Charting/Graphing, Server

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: 290894 /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Windows 7 64-bit

Vote Count: 0

Listed in the version 11.0.03.292480 Issues Fixed doc 
Code snippet:

<cfchart style="beige" width="500" height="500" showlegend="true">
    <cfchartseries type="pie" >
        <cfchartdata item="New car sales" value="50000">
        <cfchartdata item="Used car sales" value="25000">
        <cfchartdata item="Leasing" value="30000">
        <cfchartdata item="Service" value="40000">
    </cfchartseries>
</cfchart>

beige.xml file has the following property set for legend:
<legend isVisible="false" showColumnLegend="true">
<decoration style="None"/>
</legend>

Expected: legend should appear 
Actual: legend box does not appear

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3816026

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:

Attachments:

Comments:

This isn't fixed in CF11 Update 3 (11,0,03,292024(PreRelease)) and the issue exists even if no style attribute is specified. No legend is shown even in this example: <cfchart showlegend="true"> <cfchartseries type="pie"> <cfchartdata item="New car sales" value="50000"> <cfchartdata item="Used car sales" value="25000"> <cfchartdata item="Leasing" value="30000"> <cfchartdata item="Service" value="40000"> </cfchartseries> </cfchart> Basically, showlegend="true" always behaves as showlegend="false". Thanks!, -Aaron
Comment by External U.
11175 | November 09, 2014 05:41:11 AM GMT
We have logged a separate bug to track this issue: #CF-3849267 (Comment added from ex-user id:nawani)
Comment by Adobe D.
11176 | November 10, 2014 03:56:09 AM GMT