You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that I use latest version of all @mantine/* packages
What version of @mantine/* packages do you have in package.json?
7.15.1
What package has an issue?
@mantine/core
What framework do you use?
Remix
In which browsers you can reproduce the issue?
Chrome
Describe the bug
Currently, when the a tag is in a disabled state, the data-disabled="true" attribute is correctly applied, and the cursor style is updated to reflect the disabled state. However, the link is still clickable, and navigation occurs, which is not expected behavior for a disabled element.
As per the Button documentation, it is possible to prevent such behavior by using onClick={(event) => event.preventDefault()}. Could this approach be implemented for elements in a disabled state?
If possible, include a link to a codesandbox with a minimal reproduction
No response
Possible fix
No response
Self-service
I would be willing to implement a fix for this issue
The text was updated successfully, but these errors were encountered:
Dependencies check up
What version of @mantine/* packages do you have in package.json?
7.15.1
What package has an issue?
@mantine/core
What framework do you use?
Remix
In which browsers you can reproduce the issue?
Chrome
Describe the bug
Currently, when the
a
tag is in a disabled state, thedata-disabled="true"
attribute is correctly applied, and the cursor style is updated to reflect the disabled state. However, the link is still clickable, and navigation occurs, which is not expected behavior for a disabled element.As per the Button documentation, it is possible to prevent such behavior by using
onClick={(event) => event.preventDefault()}
. Could this approach be implemented for elements in a disabled state?If possible, include a link to a codesandbox with a minimal reproduction
No response
Possible fix
No response
Self-service
The text was updated successfully, but these errors were encountered: