🐞 - [V3.90.0] Button's pointer events being set to none introduces breaking changes on previously dependent logic

[JasinRefiku]

Reproduction url

https://codesandbox.io/p/devbox/focused-worker-forked-j687tg?file=%2Fsrc%2Fapp%2Fapp.component.ts%3A10%2C24

Description

With one of the changes in 3.90.0 #8478, a major issue was introduced in large code bases running versions prior that where most buttons had a hint showing why the button was disabled, or any additional info which depended on the button's pointer events.

While this may not be introduced as a bug as it's working almost exactly as described (a disabled button should have no events), with the amount of usages that depended on this logic working as it previously did, this could be classified as a breaking change.

Any instructions to properly fix this (instead of wrapping every button with a container that would hold the hint) would be well appreciated as well!

A working version: Prior v3.90 sandbox - exactly v3.88.0

Taiga UI version

3.90.0

Browser Used

Chrome

OS Used

macOS

[waterplea]

Thank you for bringing this up, We will fix that on Monday.