Second map on modal div displays inconsistently

[Pedro Guimarães]

Hi, I'm working with ol4 now in a project. I have implemented a java/spring-boot app with a main map with several WMS layers. I've also implemented a postgres search to display icons for some filtered search results. When I click on a given icon on the map, I wish to fetch other georreferenced data that is related to this point in order to draw several connection points between this main icon selected and all of its possible related points, now being fetched on the database. The thing is I don't want to display this information on the main map. I intend to freeze the main map interaction by opening a modal div containing a new ol.map instance and on this new map plot that same selecte icon fellow, now with all of its related points connected to it on the map.

This has already been implemented, with the problem that this second map does seem to present a bizarre behavior. At first, when the modal is displayed the main map information/interaction gets frozen/disabled and stays sitting in the background, as the div modal pops up to the front of the screen, displays some basic lorem ipsum and should be displaying the new map instance, only it does not. I can see the zoom buttons from the map being displayed, and only in Firefox (usually I'm on chromium-browser)  inspection mode after debbuging somehow the map started showing out of nowhere (I haven't so far been able to reproduce this behavior consistently). Most of the time, the map seems to be there (on the stack, all objects seem to be normal).

So far, I'm led to believe that there might be some CSS problem or javascript shared variables related to the ol, since everything is on the same html template, after all. I've found nothing related to problems with multiple OL maps on the same page on the internet, so I decided to try here. Any help appreciated, even knowing without more information / code snippets it might be difficult. Thanks in advance, best regards.

[Pedro Guimarães]

Well, apparently the preload: true to the tile parameter of the OSM Basemap layer solved the issue. Not sure I understand why, since all other layers didn't need that in order to appear on the main map. Perhaps someone faces the same situation.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenLayers Dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openlayers-dev/OfhXYfK6aV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openlayers-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlayers-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/openlayers-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlayers-dev/c7d46b3c-6f89-4be8-a178-3833d27bf4e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.