-
Notifications
You must be signed in to change notification settings - Fork 18
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
Pin stays on the map when results of subsequent queries return #48
Comments
Thanks for reporting. Can you share a stackblitz or something similar? |
@wipfli sure. demo is here: https://stackblitz.com/edit/web-platform-fszogw |
Does the one for the MapLibre examples work? |
Yes it will work. I've just updated stackblitz. |
Cool, I can reproduce the bug you reported. Is there any chance that you can fix this behavior? I would be happy to review a pull request... |
Maybe one has to loop through features. Here is a different example where I made only one marker being highlighted: https://codesandbox.io/s/hopeful-elion-w04kb6 |
How is the different example related to the bug? |
Maybe it is not really related :S |
Cool, thanks @xinyuluo ! |
The code after #118 should be fully typescript, which should help in solving these kind of cases, and if not, refactoring would be a lot easier. |
Can you reproduce this in the following example page: |
Hi! thanks for the amazing project. I have encountered what I think is a bug, because i think it should be irrelevant to my choice of geocoder (Nominatim).
To reproduce the bug:
Please see attached screen recording for the reference.
Thank you!
maplibre-geocoder.mp4
The text was updated successfully, but these errors were encountered: