Boundaries broken in Leaflet 10.2.11 (in Views only)

thanks for reporting this ...
BUT I can see a js console error appearing when I check the "Congressional" option ...

SyntaxError: JSON Parse error: Unrecognized token '/'

It indicates (might give the clue) that something could be wrong in that specific source data of you, or the way it is being parsed by the Drupal process. And that makes sense, as the bounding box is working fine on the "Democratic Club", isn't it?

Also please note that this Leaflet Demo page: https://www.geodemocracy.com/drupal_geofield_stack_demo/web/geoplaces-ma...
is using Leaflet module version 10.2.11 and its bounding boxing is working apparently fine (@see and check the "Content type" exposed filter on top left under the Leaflet View title ... ).

Please properly check on your specific project settings.
I couldn't reproduce your issue on the 10.2.11 version.

Thank you so much for looking into this - much appreciated.

When I mention the Congressional boundaries - and only the Congressional boundaries - in View 1 (the working example) it’s to explain why they look odd; it’s an entirely different issue than what I’m reporting here. I know what it is, how to fix it and will open a separate thread.

In View 2, the view fails on any and all boundary views; the Democratic Clubs are points, not polygons.

The data for both views is identical, so there’s something else going on that’s causing the polygons in View 2 to fail.

Would you mind verifying what I’m saying here and reopening? Thanks in advance…

Okay. May be some regression might have been introduced in bounding box on polygons.
Re-opening this ... will better check this out asap.

The "geometry" option was added to this demo Leaflet map: https://www.geodemocracy.com/drupal_geofield_stack_demo/web/geoplaces-ma...
on the Content Type exposed filter options, and all looking good also on that, that is just filtering and extending the Map bounds only to polygons geometries ...

It means to me that all is looking good in the bounding box extension also with geometries (not points).
Re-closing this as "cannot reproduce".

Figured it out. I created a "fill color" field that uses a taxonomy. In referencing the field from the View (as a label), the field defaults to "link label to the referenced entity". If that's not turned off, when the {{ field_fill_color }} token is invoked in the Leaflet Path Geometries in Leaflet settings, it borks the boundaries views. Turning it off solves the problem.

Perhaps this will help someone else... thanks for following up!