Conversation
Contributor
|
📖 Preview of ui.immich.app deployed to ui.pr-568.dev.immich.app |
meesfrensel
commented
Feb 1, 2026
jrasm91
approved these changes
Feb 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Other form inputs have cursor-not-allowed when they're disabled, but not the button. Now it does.
This also fixes a bug where the dropdown button of a
Selecthas cursor-pointer but the rest of the component has cursor-not-allowed (see immich-app/immich#25787)I think removing
disabled:pointer-events-noneis not a problem since the bits-ui button does it's own disabled checking. And since the button is disabled the browser should not activate onclicks etc.