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
I am using trackMarker / addMarker to use the spider_click event. Within it I stop event propogation as such:
self.oms.addMarker(marker, function() {
// do some stuff
event.stopPropagation();
});
This works as I want it, clicks do not go to my overlays in google maps when clicking on a marker that wont spidify and also once markers get spidify, clicking on them doesnt propogate.
The issue however is the event that causes the spidify to happen still allows event propogation. I solved this by preventing it on all marker clicks:
Although I am not happen with this solution because I wasnt sure it would even work and also it requires me to do additional listener.
It would be super useful if this was handled natively by OMS, perhaps by some sort of setting to never propogate events. Alternatively, I couldnt find an event for spidering_click that is, the click that will cause a spidering but not an actual spider_click. I tried to recreate this by listening to all clicks and then determining if the marker was would spidery, if it would then i know it was a spidering_click , but this seems better handled by OMS to expose
The text was updated successfully, but these errors were encountered:
I am using trackMarker / addMarker to use the
spider_click
event. Within it I stop event propogation as such:This works as I want it, clicks do not go to my overlays in google maps when clicking on a marker that wont spidify and also once markers get spidify, clicking on them doesnt propogate.
The issue however is the event that causes the spidify to happen still allows event propogation. I solved this by preventing it on all marker clicks:
Although I am not happen with this solution because I wasnt sure it would even work and also it requires me to do additional listener.
It would be super useful if this was handled natively by OMS, perhaps by some sort of setting to never propogate events. Alternatively, I couldnt find an event for
spidering_click
that is, the click that will cause a spidering but not an actualspider_click
. I tried to recreate this by listening to all clicks and then determining if the marker was would spidery, if it would then i know it was aspidering_click
, but this seems better handled by OMS to exposeThe text was updated successfully, but these errors were encountered: