bug(tabs): mat-tab-nav-bar tab working with space but not with enter key

[Simona25]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Previously the mat-tab-nav-bar tabs could be activated both with space and enter, while now the space key still works but the enter doesn't trigger the action anymore.

Reproduction

Link: https://material.angular.io/components/tabs/examples official material example (Basic tab nav bar)
Steps to reproduce:

1. Use the keyboard to move the focus inside the tab nav bar,
2. Pressing Enter nothing happen,
3. Pressing the Space the tab is correctly activated.

Expected Behavior

Pressing Enter the tab should be activated like when using hte Space.

Actual Behavior

Pressing Space works, while pressing Enter doesn't and the tab link isn't activated.

Environment

• Angular: 16.2.5 (but also on the 15.2.5 for example)
• CDK/Material: 16.2.5 (but also on the 15.2.5 for example)
• Browser(s): Chrome
• Operating System (e.g. Windows, macOS, Ubuntu): Windows

[zarend]

Hello folks,

Thank you for reporting this issue. I agree with the expected behavior, I would expect Enter or Space to perform the same action as clicking. We explicitly say that we support Enter and Space in the keyboard interaction documentation, it's needed to meet accessibility requirements

I investigated this issue. To summarize, both changes to the example code and implemented of MatTabNav are needed – they both seem to be handling Enter/Space incorrectly.

The example code listens for click event to update the model of the active tab. We should not be using click to update selection because it doesn't include keyboard. It would be better to listen for an output or rely on the key manager to maintain the selected tab.

There are two ways I would expect the api of MatTabNav to work.

API designs of MatTabNav

Option A, not binding to active tab and relying on KeyManager

I would expect this to look simliar to tab-group-basic-example with uses MatTabGroup and MatTab component. Binding the active or selected tab is not necessary since the key manager handles this.

<mat-tab-group>
  <mat-tab label="First"> Content 1 </mat-tab>
  <mat-tab label="Second"> Content 2 </mat-tab>
  <mat-tab label="Third"> Content 3 </mat-tab>
</mat-tab-group>

This currently doesn't work because MatTabNav seems to implement the key manager for LEFT/RIGHT arrows but not for ENTER/SPACE (selection).

I would expect MatTabNav to implement key manager for all the keyboard interactions documented in keyboard interaction.

Option B

Bind to active tab

<nav mat-tab-nav-bar [backgroundColor]="background" [tabPanel]="tabPanel" <nav mat-tab-nav-bar [backgroundColor]="background" [tabPanel]="tabPanel">
  <a mat-tab-link *ngFor="let link of links"> {{link}} </a>
  <a mat-tab-link disabled>Disabled Link</a>
</nav>>
  <a mat-tab-link *ngFor="let link of links"
     [active]="activeLink == link"> {{link}} </a>
  <a mat-tab-link disabled>Disabled Link</a>
</nav>

This currently doesn't work because MatTabNav doesn't implement @Input selectedIndex and @Output selectedIndexChange

work-around

Here's a work-around until this issue and desired API of tabs can be worked-out.

Application code can listen for (keydown) and update selection on Space or Enter.

  <a mat-tab-link *ngFor="let link of links"
     (click)="activeLink = link"
     (keydown)="setActiveLinkOnKeypress($event, link)"
     [active]="activeLink == link"> {{link}} </a>
  <a mat-tab-link disabled>Disabled Link</a>

[zarend]

Hello @mmalerba or @crisbeto (or anyone who is more familiar with tabs than me)

I was wondering if you have more information on the high level design and intention of MatTabNav. That way I can better understanding what a correct outcome would look like.

I'm confused by the API design and intentions of MatTabNav. That's because it seems to be different than our other tab components, such as MatTabHeader. MatTabHeader seems to only handle presentation and not behaviors. MatTabGroup handles more of the behaviors.

Is the intention that using MatTabNav with MatTabLink has parity with using MatTAbGroup with MatTab?

Best regards,

Zach

[Simona25]

Thank you for your answer! ^_^

[crisbeto]

@zarend the idea with MatTabNav is that it should look like a Material tab header, but have links instead of <button role="tab"></button>. It sounds like a bug that navigation doesn't work with the enter key since native links support it.

[zarend]

Yes, requirement is that end user can click link with space or enter keys. To fix this, I suggest two things:

• implementing @input selectedIndex and @output selectedIndexChange so that binding to the selected tab work for parity with MatTabGroup. Making selection model work in Option A above.
• implementing the keyboard manager so that enter and space go to the keyboard manager for parity with MatTabGroup