Simon Hampton

> Added commit that fixes issues with Elm virtual DOM after removing the map and showing it again. can't help thinking the Elm stuff should go in a seperate PR...

Hi, nice to speak again @allenhwkim. Could you take a look at https://plnkr.co/edit/HMH14FdElFQcZZVlLr5l?p=preview and press the (new) move button as that's the error I am getting

Ok, so mirroring your pattern works ``` let templateStr: string = ` Simple Marker Move `; @Component({ template: templateStr }) export class SimpleMarkerComponent { poss: { lat: number, lng: number...

Ok, I now recall that the key point in your library was that it provided access to the underlying google maps calls, so that e.g. ``` ngOnChanges() { if (typeof...

Ok, I'm fine. Do you want me to leave this issue open as a bug report on updating as an array?

If this means when my source code is in e.g. `/src` then I think I am experiencing it, and it's leading to the watches failing pretty regularly

I had a go with @Zyets suggestion and it seem to work well except near the yellow

Would appreciate an update here as I'm not sure what is the recommended way to approach the Chrome deprecation warning

Is there any solution to get juicy running on Firefox?

This is the issue I have been wrestling with too, and I think the answer is that you need to keep them out of the app and develop them separately...