Closed nicholaspretorius closed 5 years ago
I'm seeing the same issue. Working on a fix...
Any update on this? I have the same problem in my project..
Thank you!
I believe this happens because of a racing condition. I think Chrome browser tries perform faster than before. I can wrap like with a if condition
if (infoWindow.content.parentElement) {
var infoWindowContainerEl = infoWindow.content.parentElement.parentElement.parentElement;
infoWindowContainerEl.className = "ng-map-info-window";
}
v1.18.5 is released with this fix
Thank you!
v1.18.5 is released with this fix
HI @allenhwkim , when will you release this version v1.18.5 ? Thank you.
EDIT: For future reference: It is released here. //cdn.jsdelivr.net/npm/ngmap@1.18.5/build/scripts/ng-map.min.js"
Hi @allenhwkim, I really like your library, but I ran into the same bug.
When are you going to realease the mentioned version with the bug fix?
For future reference: It is released here. //cdn.jsdelivr.net/npm/ngmap@1.18.5/build/scripts/ng-map.min.js"
Hi @allenhwkim, I really like your library, but I ran into the same bug.
When are you going to realease the mentioned version with the bug fix?
Thanks for the quick reply, enjoy the day and thanks for your great work! 👍
Good day Allen,
When viewing the NgMap demo page at: https://ngmap.github.io/#/!map-lazy-load-params.html
A console error is displayed when clicking on the map marker to open the info window.
Steps to reproduce - no plunker provided as this exists on the NgMap demo page
Current behavior
Line 114 of info-window.js
var infoWindowContainerEl = infoWindow.content.parentElement.parentElement.parentElement;
Expected/desired behavior
Other information