Seems like this example broke with the upgrade to d3@6, but I haven’t diagnosed the issue yet. I’m testing on iOS so it may be related to the touch changes. Okay, fixed it. This relied on d3.mouse returning the first changed touch. I switched it to use d3.pointers to make that explicit.

A good use case for on('pointerdown')!