fix(ivy): ensure component/directive class
selectors are properly understood (#27849)
Angular allows for `<ng-content>` elements to include a selector which filters which content-projected entries are inserted into the container depending on whether or not the selector is matched. With Ivy this feature has not fully worked due to the massive changes that took place inside of Ivy's styling algorithm code (which is responsible for assigning classes and styles to an element). This fix ensures that content-projection can correctly identify which slot an element should be placed into when class-based selectors are used. PR Close #27849
This commit is contained in:

committed by
Andrew Kushnir

parent
06e5bf1661
commit
e62eeed7d4
@ -1022,6 +1022,9 @@
|
||||
{
|
||||
"name": "queueComponentIndexForCheck"
|
||||
},
|
||||
{
|
||||
"name": "readClassValueFromTNode"
|
||||
},
|
||||
{
|
||||
"name": "readElementValue"
|
||||
},
|
||||
|
Reference in New Issue
Block a user