This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(ngIf): ensure that the correct (transcluded) scope is used
- Loading branch information
1 parent
19af039
commit d71df9f
Showing
2 changed files
with
21 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d71df9f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This cause a problem when using directive with element transclusion at the root of a replacement template #9837
There is no breaking change link to this commit and it should since this cause regression when upgrading from angular 1.2 to 1.3
This is strange to disallow element transclusion at the root of a directive and I think in this case we should use $scope.$new(); and not newScope from $transclude.
WDYT ?