The features chart should have a maximum of 100%

[brunnerh]

Capping it at the most selected feature in the group is silly, it makes the bars useless.

What is the point of seeing that findLast is being 80% as used as toSorted?

[SachaG]

That's a fair point, but the downside of using 100% everywhere is that it makes other charts less readable when each item receives a small amount of votes.

So I'm not quite sure which is better…

[pwim]

This article suggests not extending it to 100%, but rather ending it close to where the data ends (the current behaviour). Some other resources confirmed that is the recommended strategy, but I didn't look deeply into it.

[SachaG]

OK, let's keep it like this for now then.

[brunnerh]

That's a fair point, but the downside of using 100% everywhere [...]

I am not suggesting that, I am only referring to features where the main thing of interest is how many people know or have used it in total and the relation to the other bars does not really matter. In the podcast example, the relative values are more interesting since the bars are more related and comparing them against each other makes sense.