For looking at the docs, is not clear to me I can add lables in both axes, all examples use at most only one, giving the feeling this feature is missing.

I would even recommend to having an example with "all the complementary info you can add".

Library looking good!

Hi @ramiy , thank you (and Lana) very much for your great work on the Charts.css! The charts look so nice, and I love the Charts.css's approach so much, that I can't help but create a binding for Charts.css for it to be used in Python. To honor the heritage, the binding is named - what else - charts.css.py, currently supporting most of the basic functionalities of charts.css, demonstrated in its doc.

It would be nice if you can add a "language binding" section in Charts.css 's doc and link to the charts.css.py project. This way you/we can better serve a segment of audience who are familiar with Python but less fluent in css.

Thanks for the framework!

Any advice on how to deal with overlapping data spans? e.g.

It would be great to have them vertically stacked on top of each other to ensure readability.

I didnt find any option for this in the docs.

Thanks for any hints!

Hi,

It'd be nice to allow showing data points on secondary axes, which currently give a sense of scale but don't allow estimating what data is roughly associated with a given bar/point.

Using the example in the documentation: there are secondary axes, but what data point (or milestone) do they represent, in relation with the bars? Secondary axe could in turn show something like “10k”, “20k”, “30k” etc.

I have a bar chart with multiple datasets in the same unit of measure, but different scales, so I'd like to be able to set data point on the secondary axes for each of them.

Thanks!

This is a great library. Data in a table is so much more usable than Google charts that we are currently using.

Would it be easy to add stacked bar charts? I.e. each bar is the stacked "sum" of multiple components? Then we could switch.

Hi Rami, I notice that there was a "1.0.0" commit recently. Another recent commit even mentioned pie chart. Is release 1.0.0 and/or pie chart coming soon? :-) Can't wait to try it out.

Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.

Below are docs for integrating FOSSA license checks into your CI:

• CircleCI
• TravisCI
• Jenkins
• Other

• Labels: consistent "block" alignment
• Data: replace data hiding method
• Labels: simpler labels alignment
• Charts: remove donut chart (will be merged to pie)
• Packages: update dev dependencies
• Chart: allow using --end variables
• Tests Pages: use --start & --end variables
• a11y: replace display:block /w visually hidden alternative
• a11y: hide data using visually-hidden() mixin
• Mixins: move the circle bg to the mixin

This resolves the warning from autoprefixer:

(1:783) autoprefixer: Replace color-adjust to print-color-adjust. The color-adjust shorthand is currently deprecated.

Looking at the samples <td style="--size: calc( 60 / 100 );"> $ 60K </td> might be more semantically valuable if we did something like

<td data-value="60" data-total="100" style="--size: calc( attr("data-value") / attr("data-total");"> $ 60K </td> or something similar... and we could have the default style for size be implicitly that calc and do similar for --start. Also would be cool to be able to reach up for the data-total value using the cascading of CSS ;)

I noticed this in the Chart Builder - if you select Line Chart, the peak is cut off for the "100" value.

Likewise, if two side-by-side bars are both at 100, the line disappears completely.

I'm noticing that when there is a stark difference in height - width ratio between table rows, it results in a varied thickness of lines along the line chart. See the picture below for an example of what I mean (notice the first line is thin and tall, and the others are thicker). Curious if this is a known issue, or if there's a known way to manipulate the css to account for this. Will look into it myself if not.

The Pie Charts page of the docs note that they are not in the current release, and suggest there is some challenge in getting them production-ready. However, there are no notes specifying what issues are present, and the CodePen example looks pretty good. Can you share what functionality is missing from getting this ready for the next release? I'd happily spend some time working on it if I knew what work was needed.

When nesting tables within <td>, the columns continue to color themselves in behind the nested table. Added a "nesting" class intended to be applied to the parent <td> element containing the nested table to indicate that the background should not be applied as it otherwise would.

Adding the multiple class allows for groupings of bars or columns, but adding stacked eliminates the groupings and instead products stacked bars/columns.

Is there an option for having groups of stacked columns?