@ -1114,7 +1114,7 @@ describe('content projection', () => {
|
||||
* being re-assigned from one parent to another. Proposal: have compiler
|
||||
* to remove all but the latest occurrence of <ng-content> so we generate
|
||||
* only one P(n, m, 0) instruction. It would make it consistent with the
|
||||
* current Angular behaviour:
|
||||
* current Angular behavior:
|
||||
* http://plnkr.co/edit/OAYkNawTDPkYBFTqovTP?p=preview
|
||||
*/
|
||||
it('should project nodes into the last available ng-content', () => {
|
||||
|
@ -562,13 +562,13 @@ describe('query', () => {
|
||||
});
|
||||
|
||||
/**
|
||||
* BREAKING CHANGE: this tests asserts different behaviour as compared to Renderer2 when it
|
||||
* BREAKING CHANGE: this tests asserts different behavior as compared to Renderer2 when it
|
||||
* comes to descendants: false option and <ng-container>.
|
||||
*
|
||||
* Previous behaviour: queries with descendants: false would descend into <ng-container>.
|
||||
* New behaviour: queries with descendants: false would NOT descend into <ng-container>.
|
||||
* Previous behavior: queries with descendants: false would descend into <ng-container>.
|
||||
* New behavior: queries with descendants: false would NOT descend into <ng-container>.
|
||||
*
|
||||
* Reasoning: the Renderer2 behaviour is inconsistent and hard to explain to users when it
|
||||
* Reasoning: the Renderer2 behavior is inconsistent and hard to explain to users when it
|
||||
* comes to descendants: false interpretation (see
|
||||
* https://github.com/angular/angular/issues/14769#issuecomment-356609267) so we are changing
|
||||
* it in ngIvy.
|
||||
|
Reference in New Issue
Block a user