angular.element.scope() returns undefined

[marosivanco]

angular.element.scope() is undefined when the application is loaded in iframe by changing the iframe src attribute.

The following code should return reference to scope but returns undefined:

angular.element(document.body).scope()

The code above is executed in the onclick handler after the document is loaded and angular has finished bootstrap:

<script>
    document.addEventListener("click", function(){
        console.log(angular.element(document.body).scope());
    });
</script>

The issue manifests itself only when the document is loaded in the iframe by modifying its src attribute.
Tested with 1.3.0-rc.5, without jquery.

[jeffbcross]

Can you provide a plnkr reproduction of the issue please?

[Toilal]

I have the same issue in my own project, but can't reproduce it using plnkr.

scope() returns undefined on any element.

Using JQLite or JQuery 2.1.1 does the same.

AngularJS 1.3.1.

[VictorQueiroz]

Try this:

document.addEventListener('DOMContentLoaded', function () {
  angular.element(document.body).scope();
});

[caitp]

are you disabling debug info in your project @VictorQueiroz?

[Toilal]

@caitp You've found it.

Enabling debug info back is a good workaround for this issue.

[gkalpak]

a good workaround

😄 😄 😄

[marosivanco]

Sorry guys for not reacting for a while. The issue is somehow related to jqCache, or more specifically to the way how expandoId is created. In older RCs, the id was created like this:
var expandoId = element[JQLite.expando];
In newer ones, the id is get using hardcoded property:
var expandoId = element.ng339;
Reverting the change solved the issue.
Unfortunately, I do not know much about the stuff, so if somebody could shed light on the functionality, then perhaps I would be able to describe the issue in more detail.

[ocombe]

Oh wow thanks @caitp that was driving me mad !
There should be a note in the doc on the $compileProvider explaining that $compileProvider.debugInfoEnabled(false) will make the scope() function return undefined, if that is the expected behavior.

Edit: my bad, it's already in the doc

Call this method to enable/disable various debug runtime information in the compiler such as adding binding information and a reference to the current scope on to DOM elements.

[ronnievdv]

Is there a way around this; having debugInfoEnabled(false), but still being able to access the scope of an element?

[gkalpak]

If you want to enable debug information temporarily (e.g. for debugging an issue on a live production app) you can use angular.reloadWithDebugInfo() as described here.