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
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
If the root element of a directive configured to be {replace:true, scope: {}}, uses another directive that also creates a isolated scope, the $compile:multidir error gets thrown
Here are a few thoughts after some discussion with @petebacondarwin:
It's not clear from this use case what the expected scope provided to ng-controller element should be. The isolate scope? A child scope of the isolate?
Given that replace is deprecated, and given that this is an edge case, should it still be considered a valid bug?
In most cases, this could simply be circumvented by nesting the ng-controller directive one element deeper than at the root node of the template.
I suggest closing as invalid, unless @IgorMinar or anyone else has some insight into a better way to support this behavior.
If the root element of a directive configured to be {replace:true, scope: {}}, uses another directive that also creates a isolated scope, the $compile:multidir error gets thrown
http://plnkr.co/edit/J4zbrndV627ERZuicyQs?p=preview
Only happens in 1.2.rc3
The text was updated successfully, but these errors were encountered: