-
Notifications
You must be signed in to change notification settings - Fork 410
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
Maps will crash (RxJS error) on identify with some WMTS layers #8724
Comments
alex-fko
added a commit
to alex-fko/MapStore2
that referenced
this issue
Oct 24, 2022
…on` parameter; geosolutions-it#8724 WMTS request identify flow fixes
12 tasks
alex-fko
added a commit
to alex-fko/MapStore2
that referenced
this issue
Oct 26, 2022
…on` parameter; geosolutions-it#8724 WMTS request identify flow fixes (geosolutions-it#8725) (cherry picked from commit 88c7ad8)
alex-fko
added a commit
to alex-fko/MapStore2
that referenced
this issue
Oct 26, 2022
…on` parameter; geosolutions-it#8724 WMTS request identify flow fixes (geosolutions-it#8725) (cherry picked from commit 88c7ad8)
The associated PR and backport for this issue have been merged, this issue can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Related support issue is #2292
This bug seems to happen exclusively with client data and an example geostory map with client data can be found here
When having a WMTS layer loaded in the TOC
performing a click
identify
on the WMTS overlay layer will crash the mapclicking on an area where an overlay layer is not there will trigger a ReduxRJs error, blocking all subsequent interactions between user and map, see below
How to reproduce
Expected Result
Current Result
performing a click
identify
on the WMTS overlay layer will crash the map.clicking on an area where an overlay layer is not there will trigger a Redux RJs error, blocking all subsequent interactions between user and map.
Browser info
(use this site: https://www.whatsmybrowser.org/ for non expert users)The text was updated successfully, but these errors were encountered: