bug(matTabLink): disabled flag prevents mouse click but does not prevent clicking using spacebar

[smorandi]

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

This is a follow up for #27071.
It claims that this issue was fixed, but it is not. Yes, preventing clicking by mouse is working fine now.
However, one can still initiate the action via keyboard by hitting spacebar when navigating to a disabled tab via cursor keys.

Navigating to disabled tabs should probably not be possible in the first place though.

Reproduction

StackBlitz link:
Steps to reproduce:
1.
2.

Expected Behavior

Setting a tab disabled should prevent mouseclicks and keyboard actions (space/return etc.)

Actual Behavior

It is still possible to navigate and activate a disabled tab via keyboard

Environment

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI: 16.0.5
Node: 16.18.0
Package Manager: npm 8.19.2
OS: win32 x64

Angular: 16.0.5
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.1600.5
@angular-devkit/build-angular     16.0.5
@angular-devkit/core              16.0.5
@angular-devkit/schematics        16.0.5
@angular/cdk                      16.0.4
@angular/material                 16.0.4
@angular/material-luxon-adapter   16.0.4
@schematics/angular               16.0.5
rxjs                              7.8.1
typescript                        5.0.4

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