AjaxToolkit Version: 4.1.7.123
Using IE9.
When populating the PieChart via code if a segment covers more than approx 50% then it isn't displayed correctly.
Code:
string[] surveyItems = new string[3] { "Yes", "No", "Don't Know" };
int[] surveyAnswers = new int[3] { 1, 5, 1 };
for (int i = 0; i < 3; i++)
{
PieChartValue pcv = new PieChartValue();
pcv.Category = surveyItems[i].ToString();
pcv.Data = surveyAnswers[i];
PieChart1.PieChartValues.Add(pcv);
}
This issue can also be replicated by 'hardcoding' the values in the aspx page.
<asp:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server">
</asp:ToolkitScriptManager>
<asp:PieChart ID="PieChart1" runat="server">
<PieChartValues>
<asp:PieChartValue Category="Yes" Data="1" PieChartValueColor=""
PieChartValueStrokeColor="" />
<asp:PieChartValue Category="No" Data="5" PieChartValueColor=""
PieChartValueStrokeColor="" />
<asp:PieChartValue Category="Don't Know" Data="1" PieChartValueColor=""
PieChartValueStrokeColor="" />
</PieChartValues>
</asp:PieChart>
Comments: I've verified it in both IE9 (Browser Mode: IE9 & Document Mode IE9) and FF11 using AjaxControlToolkit 4.1.7.123. If a PieChart has a PieChartvalue data property greater than 50% of the total values, the SVG will render the shortest distance, causing that slice of the PieChart to render incorrectly. The below hardcoded values are additional demonstrations to replicate the bug. ``` <asp:PieChart ID="PieChart1" runat="server"> <PieChartValues> <asp:PieChartValue Category="Yes" Data="49" PieChartValueColor="" PieChartValueStrokeColor="" /> <asp:PieChartValue Category="No" Data="51" PieChartValueColor="" PieChartValueStrokeColor="" /> </PieChartValues> </asp:PieChart> ``` or ``` <asp:PieChart ID="PieChart1" runat="server"> <PieChartValues> <asp:PieChartValue Category="Yes" Data="100" PieChartValueColor="" PieChartValueStrokeColor="" /> </PieChartValues> </asp:PieChart> ```
Using IE9.
When populating the PieChart via code if a segment covers more than approx 50% then it isn't displayed correctly.
Code:
string[] surveyItems = new string[3] { "Yes", "No", "Don't Know" };
int[] surveyAnswers = new int[3] { 1, 5, 1 };
for (int i = 0; i < 3; i++)
{
PieChartValue pcv = new PieChartValue();
pcv.Category = surveyItems[i].ToString();
pcv.Data = surveyAnswers[i];
PieChart1.PieChartValues.Add(pcv);
}
This issue can also be replicated by 'hardcoding' the values in the aspx page.
<asp:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server">
</asp:ToolkitScriptManager>
<asp:PieChart ID="PieChart1" runat="server">
<PieChartValues>
<asp:PieChartValue Category="Yes" Data="1" PieChartValueColor=""
PieChartValueStrokeColor="" />
<asp:PieChartValue Category="No" Data="5" PieChartValueColor=""
PieChartValueStrokeColor="" />
<asp:PieChartValue Category="Don't Know" Data="1" PieChartValueColor=""
PieChartValueStrokeColor="" />
</PieChartValues>
</asp:PieChart>
Comments: I've verified it in both IE9 (Browser Mode: IE9 & Document Mode IE9) and FF11 using AjaxControlToolkit 4.1.7.123. If a PieChart has a PieChartvalue data property greater than 50% of the total values, the SVG will render the shortest distance, causing that slice of the PieChart to render incorrectly. The below hardcoded values are additional demonstrations to replicate the bug. ``` <asp:PieChart ID="PieChart1" runat="server"> <PieChartValues> <asp:PieChartValue Category="Yes" Data="49" PieChartValueColor="" PieChartValueStrokeColor="" /> <asp:PieChartValue Category="No" Data="51" PieChartValueColor="" PieChartValueStrokeColor="" /> </PieChartValues> </asp:PieChart> ``` or ``` <asp:PieChart ID="PieChart1" runat="server"> <PieChartValues> <asp:PieChartValue Category="Yes" Data="100" PieChartValueColor="" PieChartValueStrokeColor="" /> </PieChartValues> </asp:PieChart> ```