Update leaflet to version 1.0.3 🚀 #46
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
leaflet just published its new version 1.0.3.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of leaflet.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
Leaflet 1.0.3 is a bugfix release. Changes since 1.0.2:
Bug fixes
L.Canvasredraws on several scenarios (by @perliedman, #5250, also thanks to @manubb for investigation and PR).dblclickevents in Chrome 55 due toPointerEvents (by @IvanSanchez, #5185, #5248, #5268).L.SVG.VMLfor IE8 (by @IvanSanchez, #5215).popupopenevent (by @hagai26, #5202).getBoundsZoomreturn value on CRSs with a flipped axis (by @computerlove, #5204).errorTileUrlof aL.TileLayerreturns 404 (by @IvanSanchez, #5177).L.Canvasredraw areas to avoid artifacts during partial updates (by @Ernie23, #5148).isPopupOpen()behaviour ofL.Layerwhen no popup is bound to a layer (by @gvangool, #5106).LatLngBounds.contains()to allow for non-instantiatedLatLngobjects (by @IvanSanchez, #5135).L.Control.Layerswhen thecollapseoption isfalse(by @perliedman, #5131).API changes
WrapLatLngBoundsmethod toL.CRS, to fix an issue withmaxBoundsofGridLayers (by @IvanSanchez, #5185, also thanks to @DiogoMCampos for investigation).L.Map.getSize()will now return0instead ofNaNin non-graphical environments (by @ughitsaaron, #5209).Improvements
altattribute to the<img>s of marker shadows (by @topicus, #5259).The new version differs by 3347 commits (ahead by 3347, behind by 70).
ed36a04v1.0.3c5d18fbChangelog for 1.0.3, version bump.67f12eeAvoid multiple canvas updatePaths/redraws during viewreset (#5250)2b5d401Another blind attemp to work around dblclicks on Edge (#5268)f8bccccPlugins: add magicmarkeraf72aa7IE8: Remove trailing comma in L.Layer options (#5270)ad27106Docstrings: clarify L.Browser.Touch (see #5266)7f11fdfAdd alternative text to marker shadows (#5259)7ea3ab8Plugins: add migrationLayer (#5261)d250465Merge branch 'jieter-patch-3'01a4b95Now use the correct regression fix: #513115e4456Point to correct PR for the layers control PR059a722Implement wrapLatLngBounds (to fix #5149) (#5166)694da33Blind attemp to fix Edge dblclicks (side effects of #5185) (#5248)007a63aFix typo in docstringsThere are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.