fix(autocomplete): auto-highlighted first option not display correctly if the floating label is disabled

Fixes the first option not appearing as highlighted if the consumer has set `floatLabel="never"` and `autoActiveFirstOption`. It looks like we were depending on the `transitioned` event from the label to kick off the change detection that shows the highlight.

Fixes #13734.

Author: crisbeto

src/material/autocomplete/autocomplete-trigger.ts

@@ -531,6 +531,7 @@ export class MatAutocompleteTrigger implements ControlValueAccessor, AfterViewIn
               const wasOpen = this.panelOpen;
               this._resetActiveItem();
               this.autocomplete._setVisibility();
+              this._changeDetectorRef.detectChanges();
 
               if (this.panelOpen) {
                 this._overlayRef!.updatePosition();

src/material/autocomplete/autocomplete.spec.ts

@@ -1841,6 +1841,22 @@ describe('MatAutocomplete', () => {
             .toBe(false, 'Expected no active descendant when closed.');
       }));
 
+    it('should be able to preselect the first option when the floating label is disabled',
+      fakeAsync(() => {
+        fixture.componentInstance.floatLabel = 'never';
+        fixture.componentInstance.trigger.autocomplete.autoActiveFirstOption = true;
+        fixture.detectChanges();
+
+        fixture.componentInstance.trigger.openPanel();
+        fixture.detectChanges();
+        zone.simulateZoneExit();
+        // Note: should not have a detectChanges call here
+        // in order for the test to fail when it's supposed to.
+
+        expect(overlayContainerElement.querySelectorAll('mat-option')[0].classList)
+            .toContain('mat-active', 'Expected first option to be highlighted.');
+    }));
+
     it('should be able to configure preselecting the first option globally', fakeAsync(() => {
       overlayContainer.ngOnDestroy();
       fixture.destroy();