There is a bug here. For example if you go to ADAM you get a sum total of 991 (ADAM=978, ADAMO=5, ADAMS=8) represented by two blocks (ADAMO=5, ADAMS=8, but represented as 8+978). ADAM should be be present twice, first as an intermediary node (/A/D/A/M, no weight attached) and a leaf node (ADAM) with weight 978.

Ah, tricky! Good catch Fil! I’ll look into it when I’m not busy with /K/A/D/E/N :sob:

Thanks for the suggestion! Would have taken me a bit to get around to it. Your suggestion mentioned that it may be a D3 bug, but I'm not sure if this is a super common case (where the parent has the same name as it's child and other children).

Interestingly, the same data being used in this notebook https://observablehq.com/@mkfreeman/baby-name-circle-packing now has ADAM not appear as a child of ADA? And in the collapsible tree, clicking ADAM causes nodes to flip (I imagine because they have a non-unique id...). https://observablehq.com/@mkfreeman/baby-name-collapsible-tree You should obviously be celebrating Plot Pointer interactions, not debugging this niche hierarchy issue, just wanted to document.

let's celebrate by filing an issue and fixing it for real :)

You really know how to celebrate! What is we just append a space at the end of the child with the same name as the parent “ADAM “….?

This was fixed "properly" in https://observablehq.com/@d3/treemap-parent-with-value-206 and https://observablehq.com/@d3/treemap