Closed walter-psjr closed 9 years ago
+1
can you confirm that this is still a problem? trying to replicate this problem in isolation/reduction right now.
@erwinmombay Uncomment the HTML here to see it in action: https://github.com/angular/angular-hint/blob/master/examples/profile.html#L22
thanks @SomeKittens looks like this might be caused because of us patching $watch
and wrapping the original expression with a function and passing that function on to the original $watch
. the original $watch
can no longer determine that it is a one time binding or a constant binding since we've eval'd it already. Will explore further to prove and will try some solutions.
@SomeKittens per the meeting, i'll go ahead and add code to skip any performance measurement on one time binding expressions to fix this problem and file a ticket with angular/angular.js.
Great! We can close this once the PR is in to angular-hint (and link to the angular.js issue here if you can)
got it. will work on this tomorrow morning and the weekend.
Fixed in latest, should be released with 0.8.0
I am developing an application where angular realized that the number of watchers was high despite being using one-time binding. I created a test page with a listing in table and realized that when I use http: // localhost one-time binding does not work and when I change the address for the machine name, for example, works correctly:
http://localhost/angular/repeater2.html
http://ucb-walterdev/angular/repeater2.html
The detail is that this is only happening in Chrome (I'm using version 39.0.2171.99 m, Windows 8.1 64-bit). In Firefox and Internet Explorer rendering occurs perfectly.
The code to generate the table:
Disabling the Batarang extension the one-time binding works normally.