Fix #311: split-button close controls #315
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!315
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-311"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One-click Close (completed) + not-planned dropdown segment for Close and Comment-and-Close; outside-click dismisses open menus. No backend change (state_reason vocabulary unchanged); dark+light via existing btn/card/zinc classes; keyboard support intact (menu role, arrows, Escape-with-focus-return). Incidental fix: Comment-and-Close chooser passed props.disabled (always undefined) instead of the busy guard — both split menus now disable from getBusy(). Tests: node --test full unit suite 595/595 green (incl. new web/test/unit/split-close.test.js); vite+esbuild build green. Browser check both themes left explicitly open (shared obscura daemon blocks loopback; build + headless pins verify). Closes #311.