Philippe Rivière

related https://github.com/observablehq/plot/issues/2157

@jaanli Happy to hear more thoughts about this, but would you open a [discussion](https://github.com/observablehq/plot/discussions) instead?

see https://github.com/observablehq/plot/discussions/1338

Here's a snippet that uses the new render transform: ``` marks: [ Plot.geo(perimetro_mexico, { render: (i, s, v, d, c, next) => svg`${next(i, s, v, d, c).children[0]}` // create the...

clip-path + path is still very poorly supported: https://observablehq.com/d/bf434fc5675c8f13

Chrome doesn't seem to support view-box + polygon(coords)—which works under Safari and Firefox. **Chromium bug reference: https://bugs.chromium.org/p/chromium/issues/detail?id=694218** Until this bug is resolved, we probably have to follow the classic route...

The Chrome bug has been fixed in 119 https://chromestatus.com/feature/5068167415595008 https://developer.chrome.com/blog/new-in-chrome-119 The tests in https://observablehq.com/@fil/clip-path-and-basic-shapes-1109 seem to work in all major browsers now, so we could use `style="clip-path: view-box path('${path}')"`.

"the **clip** option is set to a GeoJSON object" would be fantastic

As @jwolondon remarks in https://observablehq.com/@fil/multiscale-density-spatial-interpolator#comment-451a923b320875f1, the technique with view-box doesn't work in Safari when the page is scaled 😠 However, that's not what we're doing in #2243, which works fine...

My solution in this case is to avoid drawing the segments that go into the clipped zone. Clamping works too! But both depend on the user doing the right thing;...