-
-
Notifications
You must be signed in to change notification settings - Fork 745
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
GeoLocation accuracy-bubble going places (randomly chaning size) #2449
Comments
Thanks for taking the time to open this issue. |
I can fix a PR for this but I have some question regarding "You are not allowed to backport code from Mapbox projects which has been contributed under this new license.", especially since mapbox has fixed this bug. What exactly does this mean and what type of "fixes" would be a no go in this case? I mean since this was probobly a bug in mapbox as well but the have fixed it, will fixing it violate the copyright, or how does this work? |
It means you can't look at their code in order to fix this bug. If you haven't looked at the mapbox code related to this fix everything you do is legit. |
Alright then good, I used some code from stackoverflow: https://stackoverflow.com/a/54928479
After this change it seams to work, I will open a PR/branch. How long do you think until it is accepted and out on npm? |
A few days if you are ok with a pre-release, a bit more if not. |
I have opened a PR (#2450), doing the checklist now, it says I should confirm there is no backport, should I now look at their code? |
maplibre-gl-js version: 2.4.0
browser: Firefox
Steps to Trigger Behavior
Link to Demonstration
(you get a gif instead, but you can try it out for yourself at https://maplibre.org/maplibre-gl-js-docs/example/locate-user/)
Expected Behavior
To not do this, like mapbox does:
https://docs.mapbox.com/mapbox-gl-js/example/locate-user/
I know this is a fork of mapbox when it was still on an open license and they have since either fix this bug or something else brought it up, however I do this it should be allowed to fix such a bug that is breaking both the visuals and the function.
The text was updated successfully, but these errors were encountered: