[TabNav] Make _activeLinkChanged and _activeLinkElement public in MatTabNav component

[AncelHernandez]

Bug, feature request, or proposal:

Please make _activeLinkChanged and _activeLinkElement in MatTabNav public again, or at least protected.

The change came from: #9701

I had a tab component that extends MatTabNav and I cant access _activeLinkElement.

here's the component:

@Component({
  selector: '[vertical-tab-nav-bar]',
  templateUrl: './vertical-tab-nav-bar.component.html',
  styleUrls: ['./vertical-tab-nav-bar.component.scss'],
  changeDetection: ChangeDetectionStrategy.OnPush,
  encapsulation: ViewEncapsulation.None,
  host: {'class': 'vertical-tab-nav-bar'},
})
export class VerticalTabNavBarComponent extends MatTabNav {

  @ViewChild(VerticalInkBar) _verticalInkBar: VerticalInkBar;

  constructor(
    elementRef: ElementRef,
    @Optional() dir: Directionality,
    ngZone: NgZone,
    changeDetectorRef: ChangeDetectorRef,
    viewportRuler: ViewportRuler,
  ) {
    super(elementRef, dir, ngZone, changeDetectorRef, viewportRuler);
  }


  // /** Aligns the ink bar to the active link. */
  _alignInkBar(): void {
    if (this._activeLinkElement) {
      this._verticalInkBar.show();
      this._verticalInkBar.alignToElement(this._activeLinkElement.nativeElement);
    } else {
      this._verticalInkBar.hide();
    }
  }
}

[crisbeto]

I’m not sure they make sense as a part of the public API, but they can be made protected so they’re accessible when extending.

[AncelHernandez]

You the best @crisbeto 🥇

[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.}