-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update leaflet to 1.9.4 #824
base: master
Are you sure you want to change the base?
Conversation
I think I've figured it out and made a pull request in your repository. It'd be nice if you can verify that it works now and update this PR. |
@mjaschen found the missing piece. 👍 This PR is ready now. |
Unfortunately there's a problem which breaks the “No Go Area” feature on touch devices. tap and hold to create a circle doesn't work. I've spent some time on the weekend on the search for a fix and didn't found one. But at least I've a workaround which allows placing fixed size no go areas with a single tap on touch devices, so it's usable at least. Also, the routing library issues a call to With these two workarounds, BRouter-Web works fine with Leaflet 1.9.4 – as far as I've tested it. If I don't find any further bugs, I'll deploy it in the next days to bikerouter.de and create pull requests here. Maybe someone has an idea how to create proper bugfixes instead of workarounds. |
I don't have much time to test but I am more than happy to merge this PR when it's good enough to go live :) It'd be nice to fix the detected issues, but if it's really hard I think we can assess if that's really important (the nogo circle workaround seems good enough to me for instance). If there are other testers available to give it a try and report issues, it would greatly help! Let us know @mjaschen when your instance is live with this branch so that it's easier to test it :) And many thanks for the PR and follow-up! |
A version with Leaflet 1.9.4 was deployed to https://bikerouter.de It contains this pull request with the following additional changes:
|
This is a starting point to update Leaflet to the most recent version (solves #792).
I managed to fix the most obvious issue with the no-go-area. They are usable.
However, there is still one exception on the browser console that I couldn't solve so far.
![leaflet-nogo-areas](https://private-user-images.githubusercontent.com/10488441/370039127-89736495-3b4f-4a58-9a80-0a790128b9bd.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ5NDYwNTEsIm5iZiI6MTczNDk0NTc1MSwicGF0aCI6Ii8xMDQ4ODQ0MS8zNzAwMzkxMjctODk3MzY0OTUtM2I0Zi00YTU4LTlhODAtMGE3OTAxMjhiOWJkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEyMjMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMjIzVDA5MjIzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTdmYzk1NGUzYTVmMTNhMzU1ZmJjMTFhZTdhMjg0ZTFiNGRmODI3OTBjNjhjYTczOTUwZGRjYjM3MDg2MTliMWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.zYk-GpbdZl5nqoh1pyTXhJSul_bpAIiQp-Y_2pr69Wo)
Maybe someone else is able to fix it.