🤖 bug: workspace header buttons shift left when the skills indicator loads
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #6248 by @ThomasK33 — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in WorkspaceMenuBar and inspect how SkillIndicator is rendered while useAgentSkills loads. The issue suggests reserving the indicator's space or showing a loading state; compare both against the header layout. Done means the right-hand buttons no longer shift when skills load and the bell remains clickable during that transition.
Written by the indexing model from the issue text.
Description
The workspace header's right-hand buttons move left a moment after a workspace opens.
Cause: SkillIndicator returns null until useAgentSkills has loaded the workspace's skills. In WorkspaceMenuBar it sits right after the notifications bell, inside the right-aligned group of the justify-between header. When the skills arrive, it appears, and the bell and every button before it in that group shift left by its width plus the gap.
Impact: a click or tap aimed at the bell (or a neighbor) during that window lands on the skills indicator instead. Its hover popover opens and takes focus. The bug-bash repros hit this (#6214): the bell's popover closed right after it opened. #6220 fixes the tests by waiting for the indicator. This issue tracks the product side.
Possible fix: reserve the indicator's space (a placeholder of the same size) while skills load, or render it at once with a loading state.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 140
- Avg merge
- 2h 27m
- Merged PRs (30d)
- 873
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/xum
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug investigation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
approved backlog
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
approved backlog
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
approved backlog
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Zettlr/Zettlr#6610 · 1 comment ·
Maintainers usually reply within 1 day
-
Feil lovtekst i bekreftelsen når leder melder unntak fra oppfølgingsplanPossibly taken @AudunSorheim claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
navikt/syfo-oppfolgingsplan-frontend#1110 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
db-ux-design-system/core-web#8461 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Cannot run an integration on windows when power shell is selected as the default profile terminalOpenPriority/Blocker Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
wso2/product-integrator#2767 ·
Maintainers usually reply within 1 day