Skip to content

Upgrade Leaflet from 1.9.3 to 1.9.4 - #2274

Open
nina-mir wants to merge 1 commit into
python-visualization:mainfrom
nina-mir:bump-leaflet-1.9.4
Open

Upgrade Leaflet from 1.9.3 to 1.9.4#2274
nina-mir wants to merge 1 commit into
python-visualization:mainfrom
nina-mir:bump-leaflet-1.9.4

Conversation

@nina-mir

@nina-mir nina-mir commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

As requested in #2263 (comment).

Bumps the pinned Leaflet 1.9.3 → 1.9.4, and restores the verify_js_logs() call in tests/selenium/test_multipoints_tooltip_selenium.py that #2263 had to omit.

1.9.4 guards the unchecked layer.getElement() in _addFocusListenersOnLayer (Tooltip.js:396): Leaflet/Leaflet@v1.9.3...v1.9.4

The failing test is test_notebook[coordinate_ordering.md], but the error doesn't originate there since that page has no tooltips, and in 1.9.3 only Tooltip.js calls getElement(), from the focus-listener path that runs only when a tooltip is bound. It's the MultiPoint test from #2263 that throws. Because that test skipped verify_js_logs(), the uncaught error stayed in the session-scoped driver's console log and surfaced in whichever later test read it first.

Worth noting for future selenium tests in this repo: skipping verify_js_logs() doesn't contain an error locally, it defers it to another test.

Reproducible on main: coordinate_ordering passes alone and fails when run after the MultiPoint test.

pytest tests/selenium/test_multipoints_tooltip_selenium.py \
       tests/selenium/test_selenium.py -k "multipoint or coordinate_ordering"

Locally on 1.9.4: tests/selenium 76 passed, 1 xfailed — including the heatmap
pixel-diff test, so no rendering changes.

1.9.3's _addFocusListenersOnLayer calls layer.getElement() unguarded, so
any GeoJSON layer containing a nested FeatureGroup throws
"t.getElement is not a function". 1.9.4 guards the call.

This also restores verify_js_logs() in the MultiPoint tooltip test, which
had to omit it for that reason. Because the driver fixture is
session-scoped, the unread error stayed in the browser log and surfaced
in whichever later test read it first — which is why
test_notebook[coordinate_ordering.md] has been failing on main despite
having no tooltips of its own.
@nina-mir
nina-mir marked this pull request as ready for review August 27, 2026 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant