mat-list-option: selected/value input assignment depends on property binding order

[atscott]

The following test will fail in Ivy because selected is assigned first and then value is assigned which sets selected back to false here. This is because in Ivy, property bindings are set based on the order they appear in the template, not the order they are declared in the component.

  const itemValue = 'item1';
  @Component({
      template: `
         <mat-selection-list>
             <mat-list-option [selected]="true" [value]="'${itemValue}'">Item</mat-list-option>
         </mat-selection-list>`
  })
  class SelectionList {}

  const fixture = TestBed.configureTestingModule({declarations: [SelectionList]}).createComponent(SelectionList);
  fixture.detectChanges();
  const listItemEl = fixture.debugElement.query(By.directive(MatListOption))!;
  expect(listItemEl.componentInstance.selected).toBe(true);
  expect(listItemEl.componentInstance.value).toBe(itemValue);

I'm not sure how frequently this occurs in this repo, but other components should probably be audited for similar errors if they haven't already.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}