Inconsistent angular.element.scope() behaviour when using templateUrl in directive

[artur-charcenko]

Here's the example that demonstrates the issue. Scope ids should not match. However it works when using inline template.
It also works correctly when using jQuery v1.10.2 and templateUrl.

[caitp]

This seems to work as expected (without jQuery) with 1.2.8. But with newer versions of jQuery it seems to be an issue.

with snapshot, no jQuery

Seems like it relates to jQuery's expandostore, and I'm not sure it's a good idea to hack around it, although it is unfortunate.

I can look into a way to do this, but it might take some time. Maybe it would be worth getting the jQuery team looking at it, or something.

[caitp]

On this line,

angular.js/src/ng/compile.js

Line 1529 in c894470

linkFn(linkFn.isolateScope ? isolateScope : scope, $element, attrs,

, linkFn gets called with the correct scope passed in, but the element passed in does not have the correct scope.

This seems to be coming from the replaceWith function in the HTML compiler at

angular.js/src/ng/compile.js

Line 1676 in c894470

replaceWith($rootElement, $compileNode, compileNode);

--- the original $compileNode has the data added, but after the replacement it doesn't.

So this seems like a bug with replaceWith, I'm seeing if I can get some guidance from jQuery people on what to do about that

[caitp]

I think that's about ready ^_^ checkin-needed