[Button]: is still clickable when disabled in Firefox

[jasdelreyes]

Actual Behavior

Disabled button is still clickable in Firefox. When the button has the disabled prop set to true, the button is still clickable.

Expected Behavior

It is expected that when the disabled state is true, "interaction is prevented" as referred to in the Calcite doc.

Reproduction Sample

https://codepen.io/jasdelreyes/pen/yLQYegR?editors=100

Reproduction Steps

1. Open https://codepen.io/jasdelreyes/pen/yLQYegR?editors=100 in the Firefox browser.
2. Open the codepen link in Chrome or Safari.
3. Observe that the disabled calcite button in the firefox browser still triggers clickable events.

Reproduction Version

calcite-components 1.4.2

Relevant Info

Firefox 114.0.1

Regression?

No response

Priority impact

p4 - not time sensitive

Impact

No response

Esri team

ArcGIS Online

[geospatialem]

Looks like this is a regression introduced in 1.3.0 with #6732.

@jcfranco The HTML spec mentioned in the PR has a comment regarding Firefox behavior. The team speculates this could be a Firefox bug, but its unclear.

[geospatialem]

Research will be conducted for next steps on a fix for Firefox with the disabled button. Same as #7043 - this issue will remain open due to the workarounds mentioned below.

[geospatialem]

A workaround for FF includes adding the style="pointer-events:none" to the disabled button:

<calcite-button style="pointer-events:none" disabled id="example-button">Open modal</calcite-button>

or checking if the button is disabled in the event listener:

button.addEventListener("click", (evt) => {
  if (evt.target.disabled) {
    return;
  } else {
   modal.open = true;
  }
});

[driskull]

going to un-assign myself since @jcfranco already has this one in progress.

[jcfranco]

@geospatialem This is indeed a duplicate of #7043. Maybe we can copy any relevant information over and close this one?

Worth noting that the proposed workaround would prevent users from wiring up a tooltip with a disabled component (#5318).

[geospatialem]

Closing in favor of #7043. The workarounds, with the caveat of a tooltip with the disabled button are mentioned in #7043 (comment).