-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
map.setStyle
may result in error when used with globe
projection
#11553
Comments
@stevage Thanks so much for reporting this issue in #10784! I haven't been able to reproduce the error yet (though I suspect it's coming from this conditional). Are you setting globe view in the map parameters, and using addSource to add a geoJSON source once map is loaded? |
Yes. (As opposed to with
Yes. |
Interesting, I can't reproduce it now either, with the same codebase. I don't know what I would have changed that made a difference, but something, apparently. |
Hmm, it's intermittently reproducible. Great. http://mapswell.site44.com/geohash-map/#globe-bug¢er=4.39/-45.63/143.89 |
Ah, I'm guessing it has something to do with the maybe strange way I manipulate the map style to add styles and layers, using map-gl-utils, which calls |
@stevage Ah so this error might be specific to your set-up. Just to be sure, (if you're still experiencing this error), can you provide a minimal code reproduction of this issue in jsbin or codepen? Thanks! |
I'll close this issue as stale as we have no repro and haven't seen this issue since then, but feel free to reopen if this issue is still visible in the latest beta we published! |
I was able to consistently reproduce the error mentioned in this issue. Click map to toggle between a mercator map with dark style and globe view set in a style. After third click, I receive the same error |
@avpeery I'm reopening this issue as I've been able to reproduce this issue from latest
|
map.setStyle
may result in error when used with globe
projection
Another test case that could be used as a way to prevent regressions on the potential fix when we address that:
|
From @stevage in #10784 (comment):
version 2.8.0-alpha.1
The text was updated successfully, but these errors were encountered: