Added Leafdoc comments to Layer.js
Leafdoc comments for Popup, Layer
Leafdoc comments: L.Evented, inheritances, minor tilelayer
Leafdoc comments: gridlayer & tilelayer options
Leafdoc comments: tilelayer, marker drag
Typos
Leafdoc: switch to shorthand method params
Leafdoc: Switch to shorthands in marker drag, WMS.
Leafdoc: Vector layers
Leafdoc: Layer group, feature group, geojson
Leafdoc: LatLng, Point, Bounds, Icons.
Leafdoc: Controls.
Leafdoc: DOM & utils.
Leafdoc: "jake docs" now builds the documentation
Leafdoc: Commit actual templates instead of symlinks
Leafdoc: Fix broken build, have jake print out uglifyjs errors
Leafdoc: Several L.Map bits.
Leafdoc: Map handlers
Leafdoc: Map events, L.CRS, misc. fixes
Leafdoc: Fixed ordering of classes by using new leafdoc features
Leafdoc: Misc bits at the bottom of the docs
🍂doc: Map panes
🍂doc: CRSs, projections and their templates
🍂doc: miniclasses for map methods' options
Leafdoc: Cleanup L.Class, mark uninheritable sections, use Leafdoc 0.3.0
🍂doc: miniclasses for event types, bump to Leafdoc 1.0.0
🍂doc: Make linter happy after branch rebase
🍂doc: Tweaked headers for inherited stuff.
🍂doc: Tweaking section headers (white, padding, triangles)
Leafdoc: upgrade to 1.2, document SVG&Canvas, and misc bits
🍂doc: minor CSS tweaks, version in filename, typo.
Add missing bits - supersedes #4105, #4065, #4031🍂doc: moved sections around, minor typos & fixes
Typo about LocationEvent
Symptom: Switching between layers with different attributions does
not remove the attribution from the previously selected layer.
Control.Attribution keeps track of its attributions with a counter for
each text. The problem described in #4285 is that each time the layer
is added to the map, the counter is increased by two. It's because
Layer calls Control.Attribution.addAttribution() twice, once from
addLayer() and the second time via the whenReady() callback _layerAdd().
This was not caught by the tests since the callback was never fired
(missing map.setView() call).
Fixes#4285
A lot of plugins use the capitalized internal constructors rather than
the API. This should broaden legacy support for plugins that use the
L.Circle constructor.
Otherwise, we may have bug when polyline latlngs are cleared while
not updating the polyline bounds (so ending with empty latlngs
but this._bounds still valid).
