-
Notifications
You must be signed in to change notification settings - Fork 0
🎨 Palette: Add explicit focus rings to ImageUploader buttons #54
New issue
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
Open
MacTechIN
wants to merge
1
commit into
main
Choose a base branch
from
palette/focus-rings-image-uploader-3804850135737298172
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| ## 2026-02-15 - [Absolute Positioned Buttons in Overflow-Hidden Containers] | ||
| **Learning:** Keyboard focus rings on absolute positioned interactive elements (like overlay action buttons) within `overflow-hidden` containers can frequently get clipped, degrading visibility for keyboard users. | ||
| **Action:** Always combine standard focus-visible classes (`focus-visible:ring-2 focus-visible:ring-offset-2 focus-visible:outline-none`) with a shadow property (e.g., `shadow-lg`) or sufficient internal padding to ensure the focus ring remains fully visible. Adapt ring colors logically to the action context (e.g., destructive actions like 'Remove' should use red). | ||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The action item suggests combining focus-visible classes with a shadow property (like
shadow-lg) to prevent focus ring clipping inoverflow-hiddencontainers. However, in CSS/Tailwind, bothshadowandringutilities are implemented usingbox-shadow, which will both be clipped byoverflow: hiddenif they extend beyond the container's boundary.In the implementation of
ImageUploader.tsx, the focus ring is not clipped because the absolute-positioned button is placed as a sibling outside of theoverflow-hiddencontainer (inside the parentrelativewrapper), which is the correct way to avoid clipping.Consider updating this learning note to clarify that placing the interactive element outside the
overflow-hiddencontainer (or adding sufficient padding/margins to the container) is what actually prevents clipping, rather than adding a shadow.