You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a polymer element in an angular app, I noticed that Batarang is no longer able to report the scope attached to DOM elements. And the angular.element( <node> ).scope() that I wanted to use inside my polymer element to access my model doesn't work either, of course.
After a little bit of research I found that it had to do with the ShadowDOM wrapping, and patching the jqLiteExpandoStore and jqLiteData functions of Angular would solve the issue: I added window.unwrap && ( element = unwrap( element ) ); at the beginning of each of these functions (and jqLiteRemoveData as well).
I haven't been able to find exactly what needs to be changed in Polymer to avoid patching Angular. I hope you guys can help me out.
It might have to do with the expando thingy, which is a randomly named property that links data from a single cache to DOM elements.
The text was updated successfully, but these errors were encountered:
I'm not familiar enough with Angular to replicate this scenario from your description. Can you link me to an example, or give me the steps that would expose the issue?
When using a polymer element in an angular app, I noticed that Batarang is no longer able to report the scope attached to DOM elements. And the
angular.element( <node> ).scope()
that I wanted to use inside my polymer element to access my model doesn't work either, of course.After a little bit of research I found that it had to do with the ShadowDOM wrapping, and patching the
jqLiteExpandoStore
andjqLiteData
functions of Angular would solve the issue: I addedwindow.unwrap && ( element = unwrap( element ) );
at the beginning of each of these functions (andjqLiteRemoveData
as well).I haven't been able to find exactly what needs to be changed in Polymer to avoid patching Angular. I hope you guys can help me out.
It might have to do with the
expando
thingy, which is a randomly named property that links data from a single cache to DOM elements.The text was updated successfully, but these errors were encountered: