New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EnhancedLegendRenderer incorrectly strike through the label #195
Comments
i stumbled on the same issue, legends with showSwatches:false do this :( as a workaround, is there away to turn on swatches but redefine their appearance/size/shape/colour/transparency to be virtually invisible? update: interesting... |
i fixed the bug for me (in jqplot v1.0.9), seems to behave better than not fixed -- but i have NOT tested all possible cases or looked for other side effects. in jqplot.enhancedLegendRenderer.js i changed the else clause in doLegendToggle function to now be:
|
Hi developers,
I am using jqplot in my project now and have the problem with EnhancedLegendRenderer.
Detail:
My page is using the bar chart with EnhancedLegendRenderer, for the feature to toggle on/off series.
When clicking on the label of the chart, the corresponding serrie is filtered out but the legend is striked through incorrectly.
Step to reproduce:
Look at the chart with 3 legends above. When I click to the legend "label 1", the corresponding bar is filtered out. However, the stroked through legend is not correct. It strikes through "label 3" instead of "label 1":
Same thing happens if I click to the legend "label 3", the "label 1" is stroked through.
Clicking to "label 2" has no problem, it strikes label 2 correctly.
Expected:
The bar is filtered out, the label is stroked through correctly
Note:
I found the example in the link below having the same problem
http://www.jqplot.com/examples/blockPlot.php#
The second chart has kinda similar problem with my problem. When I click to "Independant Brands" it strikes "Coke brands" instead.
Clicking to "Pepsi brands" and "Coke brands", it strikes nothing.
The text was updated successfully, but these errors were encountered: