RFC 7946 was officially published in August 2016, i.e. before Leaflet version 1.0.0 (Sep 2016). The previous GeoJSON spec website (geojson.org) displays a big "obsolete" disclaimer on it, making it confusing for developers which version they should refer to. Replace the link to use the RFC that was in use at that time, on all HTML docs since it was available, i.e. from Leaflet 1.0.0.
for current API documentation version (1.3.0/1.3.1) so that it is up to date. It is likely that this docs version will remain the current one for quite some time, given the release pace.
* test(GridLayer): add zoom-in for graph browser
Add a new test for "graphical browsers" for zoom-in animation, not relying on sinon.useFakeTimers so that it lets the animation executing on its own, and is less prone to breaking when the animation process is changed internally.
* test(GridLayer): add zoom-out for graph browsers
Add a new test for "graphical browsers" for zoom-out animation, not relying on sinon.useFakeTimers so that it lets the animation executing on its own, and is less prone to breaking when the animation process is changed internally.
* trying to run tests in FF
* run tests in PhantomJS first
* add chrome test run to travis
* Revert "add chrome test run to travis"
This reverts commit 933f7b5e038722b18b62180edfe4cf19aadc11ab.
* update Firefox test script in Travis CI
* use latest version of Firefox in TravisCI tests
* fix firefox artifact signature in travis config
* trying to set screen size with xvfb-run
* increase screen size
* remove DISPLAY env variable
to Frameworks & built systems section.
Added as first plugin in list, so that developers have less chance missing it, and it is useful to many integrations.
because graphical browsers, even in non-animated pan, will still perform tile fade-in animation, which require some frames before calling _pruneTiles().
because graphical browsers, even in non-animated pan, will still perform tile fade-in animation, which require some frames before calling _pruneTiles().
test on number of pruned tiles during zoom-out in "graphical browsers" (i.e. not PhantomJS) was failing due to incorrect interleaving of rAF and grid.once('load') event listener, not matching the current animation algorithm.
test on number of pruned tiles during zoom-in in "graphical browsers" (i.e. not PhantomJS) was failing due to missing some rAF to let the animation process fully go through and be able to prune the remaining 4 tiles.
* test(Map): set div width for getBoundsZoom inside
in particular Firefox has a different default width than PhantomJS, making the result different than the expected one. Wider container => can zoom higher to fit the specified bounds.
* docs(Map): getBoundsZoom add padding
3rd argument docstring.
