Mike Bostock

I appreciate the exploration and quick fix to the docs. The optimized approach seems slower than the notebook version, I think because the filter transform only applies to rendering after...

Nice, that’s much faster. Because of the way we share properties with G elements, it would be hard to implement the **zIndex** option across marks & facets (without native SVG...

That doesn’t seem right. First, _selection_.interrupt is provided by d3-transition, not d3-selection. And second, _selection_.interrupt has existed since version 0.0.5 of d3-transition; see https://github.com/d3/d3-transition/commit/46bbcd660aec3ee8c8811d57552f8f7711880dab. You probably have a different issue...

A related idea here would be to have a **pointerScope** option that controls the scope of the pointer state such that multiple plots could share the same exclusivity. The current...

Maybe we can call it the “clicker” interaction in homage to TLOU. 😂

A quick workaround for this is that you can use _event_.stopPropagation on _pointerdown_ events to prevent the pointer interaction from becoming sticky. Another approach is to emit a _pointerleave_ event...

The `strokeWidth` channel is not bound to a scale, so you can only it express it as literal values (currently). As you discerned, you’ll need to say something like `strokeWidth:...

I like the idea of subplots or “subfacets” that share scales but can be positioned arbitrarily in x and y.

Yes, but with shared scales. I think it would be a similar mechanism to how facets currently work, with the difference being that you can position the facet arbitrarily in...

This reminds me of CSS’s [margin-block](https://developer.mozilla.org/en-US/docs/Web/CSS/margin-block) and [margin-inline](https://developer.mozilla.org/en-US/docs/Web/CSS/margin-inline), which are logical directions that depend on the orientation of text. Would it be sufficient to just have a single offset that...