* Vertical lines while moving over canvas elements
* Vertical lines while moving over canvas elements
* bounds.min._floor(); bounds.max._ceil(); instead
* Rounding bounds in _redraw function instead of _clear function
* Adds initial tests for L.Layer#popup
* Fixes Layer.isPopupOpen when no popup is bound
This fixes uncaught exception when checking whether a popup isOpen(),
when the layer has no popup bound to it.
* Update Projection.leafdoc
To me it appears that the property bounds expects 'Bounds' and not 'LatLngBounds'. All the included projections pass 'Bounds'. Giving the area where the projection is valid in latlng's did not work for me.
* Update Projection.leafdoc
* This is a routing implementation from AMap(高德地图),you need set a location points and key,Leaflet.Routing.Amap will generates colorful route. Because of most china map use unique Projection , include AMap, this should be attention.so I import Project class for projection transform.
* English grammar for L.Routing.Amap
* Use openstreetmap.org, not osm.org
osm.org is a convenience redirect for typing into your browser URL bar, and not an officially supported services endpoint (for example, it doesn't have the SSL certificates you might otherwise expect)
* Update reference-1.0.2.html
* Update TileLayer.js
* Finish drags when a L.Draggable is removed, fix#5063.
* Use L.Draggable._dragging to check if we should stop the drag
* Add Draggable.finishDrag to allow finishing drag programmaticaly
Out of any event.
* Ensure zoom is within span when adding a layer with min/maxzoom, fixes#4915.
* Add tests written by @theashyster
* Add tests to verify map's zoom is actually adjusted to layer's min/max
`addData`, `resetStyle` and `setStyle` methods of `L.GeoJSON` actually return `this` (the current GeoJSON Layer Group), not any Layer.
Can be especially confusing in the case of `resetStyle`, where we pass a layer as argument, and with `addData`, which can accept a single GeoJSON feature, hence we could (mistakenly) think that it returns the newly created layer.
detailed that modifying `L.Icon.Default.prototype.options` only customizes the icon, but it remains an image-based icon.
Added a paragraph about completely replacing the default icon, so that it can now be anything (including a divIcon).
