You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi !
Same as Issue 1101 I wanted to cancel the expansion of cluster based on condition.
But it seems like i cannot stop the propagation of the events.
I tried the solution "attach the event handler before any layer is added to L.MarkerClusterGroup" but the cluster keeps expanding. Maybe there is something I dont understand about leaflet layer and event.
How to reproduce
Leaflet version I'm using: 1.9.4
Leaflet.MarkerCluster version I'm using: 1.4.1
Browser (with version) I'm using: Latest firefox
OS/Platform (with version) I'm using: Macos
What behaviour I'm expecting and which behaviour I'm seeing
Im expecting the cluster to not open while clicking and another condition (in my example command key). I already logged, I'm entering the condition
Im seing the cluster to expand and the map to zoom
I followed the step here https://github.com/Leaflet/Leaflet.markercluster/blob/master/CONTRIBUTING.md to generate the js source file from master. It's not an official version of this plugin, but since I saw a commit related to this issue. I tried my luck and it seems like working as intended and the event is blocked.
Hi !
Same as Issue 1101 I wanted to cancel the expansion of cluster based on condition.
But it seems like i cannot stop the propagation of the events.
I tried the solution "attach the event handler before any layer is added to L.MarkerClusterGroup" but the cluster keeps expanding. Maybe there is something I dont understand about leaflet layer and event.
How to reproduce
What behaviour I'm expecting and which behaviour I'm seeing
Im expecting the cluster to not open while clicking and another condition (in my example command key). I already logged, I'm entering the condition
Im seing the cluster to expand and the map to zoom
Minimal example reproducing the issue
jsFiddle
The text was updated successfully, but these errors were encountered: