Native click event is not triggered by click on a disabled button

[Nikolaj1010]

What is your Test Scenario?

I need to check that native click event is triggered by click on a disabled native button

What is the Current behavior?

Native click event is not triggered by click on a disabled button

What is the Expected behavior?

Native click event should be triggered by click on a disabled button

What is your web application and your TestCafe test code?

The issue can be reproduced here: https://stackblitz.com/edit/angular-ivy-gldr6d?file=src%2Fapp%2Fapp.component.ts or https://stackblitz.com/edit/angular-ivy-gldr6d

I am able to triggered native click event by click on disabled button manually but the native click event is not triggered in TestCafe.

Steps to Reproduce:

1. Go to https://angular-ivy-gldr6d.stackblitz.io/
2. Click on "Disabled native button"
3. See that the button has been native-clicked 1 time but the same steps do not trigger the event using TestCafe

Your Environment details:

• testcafe version: 1.8.2
• browser name and version: Chrome 83.0.4103.106
• platform and version: Windows 10

[Farfurix]

@Nikolaj1010

Hello,

I've reproduced the issue under Windows 10 / Chrome 83. We'll examine it and check for a suitable solution.

For the team:

import { Selector } from 'testcafe';
import { waitForAngular } from 'testcafe-angular-selectors';

fixture `Fixture`
    .beforeEach(async t => {
        await t.debug(); // Here we need to unlock the tested page and ckick the "Run this project" button

        await waitForAngular();
    });

test
    .page('https://angular-ivy-gldr6d.stackblitz.io/')
    ('test', async t => {
        const nativeBtn   = Selector('#nativeBtn');
        const clicksCount = Selector('#nativeClickBasicBtn').innerText;

        await t
            .click(nativeBtn)
            .click(nativeBtn)
            .click(nativeBtn)
            .click(nativeBtn);

        await t
            .expect(clicksCount).eql(4);
    });

Possibly related to DevExpress/testcafe-hammerhead#2346. Update: this fix doesn't resolve the issue.