Closed lukaszTrackback closed 8 years ago
I'm seeing something similar with batarang 0.10.7 and angular v1.4.9.
Here's a screen shot of some watches that are still showing up as triggered. (uploaded to imgur because github's file upload kept flaking out).
I don't see this issue on my side. Windows 7, latest chrome. Btw it is 'one time bind' and not 'one way bind'
This issue was fixed some time ago. Make sure you're on the latest version. Will reopen if there's a repro case against the latest version.
I have the same problem on Chrome for Mac with Batarang 0.10.7 and angular 1.5...
@EricBorlandAGS That's nice but useless without a repro case. Can you post a snippet of code that reproduces the problem?
I also have this problem. Verson 0.10.7, Google Chrome 51.0.2704.106 (Official Build) (64-bit), ubuntu 14.04.
f I run simple code under Windows 10 Chrome (tested on angular 1.4.9 and 1.5.0) and enable Batarang(0.10.7) angular seems to ignore one time binding. More.