-
Notifications
You must be signed in to change notification settings - Fork 0
fix(settings): responsive Permissions matrix, black-on-yellow tag ink, drop Theme row #229
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
kateebonner
wants to merge
3
commits into
local/amicode
Choose a base branch
from
kate/settings-permissions-responsive
base: local/amicode
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.
+435
−150
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
b8c9996
fix(settings): responsive permissions matrix, black-on-yellow tag ink…
kateebonner 6d61d46
fix(settings): permissions matrix as settings rows, full-width card, …
kateebonner 5c38d13
fix(settings): permissions tier = Everywhere defaults + folder except…
kateebonner 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
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
Oops, something went wrong.
Oops, something went wrong.
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.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 24496
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 9365
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 17536
🌐 Web query:
Kobalte Select aria-label forwarded to Select.Trigger root component accessibility💡 Result:
Yes, the aria-label property passed to the Kobalte Select.Trigger component is correctly forwarded to the underlying root element [1]. In the Kobalte Select implementation, Select.Trigger is designed to accept standard ARIA attributes, including aria-label, which it then applies to the rendered button element [1][2]. Official testing code confirms that providing an aria-label to the Select.Trigger component results in that attribute being successfully applied to the DOM element [2]. When you use Select.Trigger, it acts as a wrapper that manages various accessibility requirements, such as aria-haspopup, aria-expanded, and aria-controls, while allowing you to pass through custom accessibility labels like aria-label and aria-labelledby [1]. This ensures that assistive technologies receive the appropriate descriptive information for the select input [3][4].
Citations:
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 21459
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 289
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 263
🌐 Web query:
site:kobalte.dev/docs/core/components/select aria-label Select💡 Result:
The aria-label attribute is an ARIA property used to provide an accessible name for an element when no visible label exists in the document [1][2]. It is frequently used in user interface components, such as select triggers or buttons, to convey the purpose of the component to assistive technologies like screen readers [1][2]. In practice, the aria-label serves as a concise string that describes the element's function. For example, a select component might use it on its trigger element to identify the purpose of the selection, such as aria-label="Fruit" [1][2]. Key considerations for using aria-label include: 1. Labeling Purpose: It should only be used when a visible label (such as a standard HTML label element) cannot be provided or is not appropriate for the design [1][2]. 2. Conciseness: The label should be short and descriptive, focusing on the action or the category of the input [1][2]. 3. Precedence: Assistive technology will use the aria-label as the primary name for the element, overriding other less explicit naming methods [1]. In modern web development libraries like Kobalte, aria-label is typically applied to container or trigger elements to ensure that interactive components are properly announced to screen reader users [1][2].
Citations:
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 235
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 475
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 4658
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 13733
🏁 Script executed:
Repository: harmoniqs/opencode
Length of output: 14661
Give each permission selector an accessible name.
The selected effect alone does not identify the action or directory. Pass an action- and pattern-specific
aria-labeltoSelectV2.Proposed change
<SelectV2 + aria-label={`Set ${GROUP_LABEL[group]} permission for ${isDefault ? "everywhere" : pattern}`} appearance="inline"📝 Committable suggestion
🤖 Prompt for AI Agents