[master] infoWindow does not update content based on $scope variables

[franklindner]

I want to show the distance and duration between two markers in an infoWindow. Those variables are getting updated every 10 seconds as a result of a request and changing marker positions. I can print out $scope.distance.duration it is getting updated nicely but the infoWindow never shows them.

HTML:

Distance: {{ distanceMatrix.distance.text }} | Duration: {{ distanceMatrix.duration.text }}

Could this be an issue or am I just doing it wrong?

[nmccready]

What branch and a jsbjn or fiddle w the similar issue would help.

[nmccready]

Master branch correct?

[franklindner]

Correct, I was using the master branch. I had not found time to prepare the jfiddle till today sorry.

[giacomorebonato]

Is there a branch where this problem is solved?

[nmccready]

Have you guys tried replacing references besides just updating the data on the same reference? Also is there a jsbin with this issue already?

[ghost]

I came across the same issue and created a plunker to show the exact problem

http://plnkr.co/edit/tHU3OK8SW1M5YzEMxz5n?p=preview

[cthrax]

I've verified this is true on develop as well. Both with a value and a reference. http://plnkr.co/edit/JIFneB5rzcgK42gL8BJM?p=preview

[nmccready]

Anyone want this?

[cthrax]

I could take a look, but likely not until Sunday.

[nmccready]

Done

[cthrax]

I haven't been able to determine root cause on this yet, I'm suspecting though that the window is cloning the compiled element we pass them and therefore angular no longer has a reference to it, but I haven't been able to prove it. I can just see that the content in the window does not change, but the content in the directive does.

[nmccready]

I am pretty sure #382 and this are dupes. It is probably related to show as using "show" is required now to get a Window visible.

[nmccready]

BTW has anyone tries replacing the Window Reference? It may not be enough to change scope variables. Depends on how deep the watch is.

[cthrax]

@nmccready I tried replacing a property on an object (versus a scalar) and an object itself, to no effect.

[nmccready]

crap, well I'll get to it after I do 154, and 74.

[nmccready]

Which directives are causing the issue? markers w windows? or markers w window? If anyone is using markers with windows.. I again will stress against this. markers w window is way better performance and memory wise. Especially if you only need to show a few (1 or more where starting from close) at a time based on click.

The only time windows is optimal is if you need all the windows open from the start. Or if your using Windows as your (css markers that are windows) markers.

[ghost]

In my plunker I am only using a window. But in ticket #382, I'm using markers w window.
Either case, no windows

[cthrax]

For posterity, I have a plnkr demonstrating that it's an issue with the way html is being compiled into the infowindow content. http://plnkr.co/edit/z9Ab89kbkHmFC2AXzTnD?p=preview . Not sure what to do about it at this point, but root cause is known now.

[nmccready]

Issue #382 and this may go hand in hand. I am looking at 382 now but I may resolve this at the same time.

[nmccready]

@cthrax if you continue on this, I would fix this in develop only.

[nmccready]

@franklindner can you verify the same issue on the develop branch.

[nmccready]

Ok this is with window, can anyone verify the issues with windows, and window, and windows inside marker or markers?

[nmccready]

I am almost 100% positive this is the same issue as #382

[nmccready]

I take that back this is an issue

[nmccready]

I think @cthrax and myself have narrowed the issue down. One of us will get to it this evening.

[nmccready]

We may have to do something similar to this (search for slit wrists) http://stackoverflow.com/questions/19304559/how-to-watch-the-dom-for-changes-angularjs . However we will be just checking for element.html() differences.

[nmccready]

I have some of it fixed, so far window is fixed. Still working on windows

[nmccready]

@cthrax did you get anywhere with this as well?

[cthrax]

@nmccready I did not. I tried watching the dom tree of the attached element and it did not fire on changes. Then I saw that you had fixed that part of it, so I didn't revisit.

[nmccready]

@cthrax I figured it out and the fix is crazy simple for windows. I wish I would have thought of it before!

[nmccready]

fixed via 8f286b1

[cthrax]

Nice, just always compile it. Hindsight is 20/20, but I'm feeling a little bit like "duh" now.

[knitzie]

Hi,
I just found this issue and updated the bower package on my project to solve my issue.
Now I've got a strange behaviour: After first click on the marker, the window opens empty. On second click, the content is available.
I forked a fiddle and add a random variable (windowOptions.show) to the html content:
http://jsfiddle.net/martgvd0/

FYI:
In my case, I want to update the window content with the markers data (like the address).

Does anyone else got this issue too?

[nmccready]

@knitzie please create a new issue.