Load event may get lost about leaflet-gpx HOT 3 OPEN

Very good points. Overloading onAdd(map) would definitely solve the issue, but in terms of "API" for L.GPX I like the fact that you can "prepare" your layer by creating it (var gpx = L.GPX(data);), and eventually use some of the methods it provides, before adding it to a map instance of your choice. It feels weird to be that parsing/loading the data is somehow tied to adding the layer to the map.

I guess another solution is to overload addTo(map) but for different reasons: when adding to the map, we could check if the data has been loaded already and fire the loaded event manually. This would cause the event to potentially be fired twice in most cases though.

from leaflet-gpx.

Maybe we should look at the behaviour of some existing layer classes within leaflet which also do asynchronous loading. I can think of the tile layers only at the moment, and these definitely only start loading once you add them to a map.

from leaflet-gpx.

Don't forget that JS is single threaded. On Load event cannot be processed until your code returns to event loop. Therefore the code is completely fine.

from leaflet-gpx.