Now that tile.openstreetmap.org supports HTTP/2 + HTTP/3 the old (a|b|c).tile.openstreetmap.org is no longer recommended.
Use tile.openstreetmap.org directly is faster and will likely result in a better cache hit ratio.
Signed-off-by: Grant Slater <git@firefishy.com>
Signed-off-by: Grant Slater <git@firefishy.com>
* Control.Layers: clean up (continue e287b5ec1531238aaf4c4e5f5bfee51b5a577954)
* Control.Layers: stop relying on Browser `android` and `touch` properties
- `android` is useless here, as there are a lot of non-android touch devices (including desktop ones)
- `touch` is useless, as mouse can be used on touch-screen too
Now these usecases are covered:
- `mouseenter/leave` are handled on touch devices too
- If Layers control created with {collapsed:false}, and than it collapsed explicitly
[using .collapse() method], it's now possible to expand it back with click.
* Control.LayersSpec.js: add test for toggle focus
* Control.Layers: fix unexpected layer switch when expanding control on touch
Most browsers produce compatibility mouseenter for touch event, but not all,
so we listen for click also.
The problem is that these compatibility events come all in single batch, so
same touch induces expand and then immediate input switching.
To avoid this we temporarily prevent click on layers section.
Note: more straight-forward way would be relying on e.sourceCapabilities.firesTouchEvents,
but atm it has rather low support: https://caniuse.com/#feat=mdn-api_inputdevicecapabilities_firestouchevents
* Deprecate Browser.android23 property
* Deprecate Browser.androidStock property
* Remove legacy android workaround
* Remove legacy android Chrome workaround
* Deprecate Browser.android property
As we do not rely on it anymore
User agent sniffing is evil, and we should not support it 'just in case'.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent
* Doc: remove statement about Android legacy support
* Changelog and blog post for 1.7.0
* Tweak test for finger drag
Apparently, some of the changes related to pointer events have made that touch-dragging less than the threshold now force a recalculation of the map center - the value is the same, so is == equal to the previous center but not === the same LatLng instance.
* Bump to v1.7.1; fix uglifyjs script; update integrity hashes
* Website stuff updated for 1.7.1
* Update CHANGELOG.md
Co-authored-by: Vladimir Agafonkin <agafonkin@gmail.com>
* Update docs/_posts/2020-09-03-leaflet-1.7.1.md
Co-authored-by: Vladimir Agafonkin <agafonkin@gmail.com>
* docs: 1.7.1 release announcement tweaks; delay dates by one day
Co-authored-by: Vladimir Agafonkin <agafonkin@gmail.com>
* update changelog
* add blog post
* build docs
* update reference and download pages
* add new version
* update config and announcement
* update integrity hashes
* update changelog
* add blog post
* generate api dosc
* update reference to redirect to the new version
* update latest verstion on download page
* update reference-versions
* update version in config.yml
* update announcement
* update integrity hashes
* update changelog
* add blog post
* update reference
* update download page
* update version in config.yml
* update announcement
* point reference.html to 1.3.1 docs
Also add reference-1.3.1.html, which redirects to 1.3.0 docs
* update integrity hashes
* redirect reference.html directly to 1.3.0 to avoid double redirect
* Add documentation on how to do a release
* Preliminary changelog for next release
* Preliminary blog post
* Modify version to 1.2.0
* Update changelog
* Add 1.2.0 reference
* Point to 1.2.0 docs
* Update hashes and latest version
* Update latest news
* Add 1.2.0 release date
