joshmorony suggested using NgZone if you were running code outside of angular’s zone, causing the UI to not update fast enough. Because @pdj is using a map just like I did, and is facing the same issue that I did, I didn’t think it any harm to give him the same solution that worked for me : forcing code to run inside angular’s zone, especially when working with maps, where code seems to be running outside of Angular’s zone.
I don’t think anything is necessarily broken. Maybe angular loses scope when you’re using the map. If you can come up with a better fix than this, I think we would all appreciate it. If you can’t, then let’s not plead people to not implement something that works for them.