Open marcorinck opened 11 years ago
I could fix this with adding "href='#'" additionally to the ng-href attribute on the anchor.
So this:
<a ng-href="{{dokument.link}}" ng-class="{'irrelevant': !dokument.relevant}" target="_blank">{{dokument.name}}</a>
got to this:
<a href="#" ng-href="{{dokument.link}}" ng-class="{'irrelevant': !dokument.relevant}" target="_blank">{{dokument.name}}</a>
Hi, ok, great that there is a workaround! Will debug into this when there is a little more time...
Tobias
I was having a delayed glitch in colour of link while using ng-href. when I added href="#"
it stopped.
That was weird. :angry:
I have a strange problem with ng-href in my project after updating to latest version of angular adapter 1.3.1
I have created a fiddle to demonstrate how the structure of my page is and what the user has done before the error happens. But I can't replicate it in the fiddle, maybe it has to do with some side effects of other parts of my page, f.i. the second page is in a seperate html file, which I can't emulate in jsFiddle (I don't use any user-defined routes in this project, I only call $location.url("some.html") Anyway, here is the fiddle: http://jsfiddle.net/marcorinck/jsBZh/3/
Basically, I have some links which are generated with ng-repeat. The links are part of data which are loaded from the backend via $http. The page transition after clicking on the page link only happens after data was successfully loaded via $http.
If I use ng-href for the links so that angularJS can generate the links correctly, one of two things happen after navigating to this page:
If I use only href attribute for the links, its working correctly, but links are corrupt (which is normal when using angular expressions in href).
Very strange.