We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cursor: not-allowed is not default behavior for disabled elements (cursor: default is)
cursor: not-allowed
cursor: default
It is not compatible with pointer-events: none when applied on the same element.
pointer-events: none
If you do want both, you would always need to apply cursor: not-allowed on a wrapper/container element and have the children be pointer-events: none.
For default html elements like button and select, this can be done with an overwrite:
:disabled { cursor: not-allowed; } :disabled > * { opacity: 0.5; pointer-events: none; }
For Skeleton there probably needs to be a decision whether to follow browser defaults or apply cursor: not-allowed in a consistent way.
This ticket should be used to investigate it, the outcome would be a ticket to implement the consistency throughout the library.
Enhancement
No response
The text was updated successfully, but these errors were encountered:
Note for myself: we set the disabled state styles within the plugin > core.css styles (aka global styles).
Sorry, something went wrong.
No branches or pull requests
Describe the feature in detail (code, mocks, or screenshots encouraged)
cursor: not-allowed
is not default behavior for disabled elements (cursor: default
is)It is not compatible with
pointer-events: none
when applied on the same element.If you do want both, you would always need to apply
cursor: not-allowed
on a wrapper/container element and have the children bepointer-events: none
.For default html elements like button and select, this can be done with an overwrite:
For Skeleton there probably needs to be a decision whether to follow browser defaults or apply
cursor: not-allowed
in a consistent way.This ticket should be used to investigate it, the outcome would be a ticket to implement the consistency throughout the library.
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response
The text was updated successfully, but these errors were encountered: