Repository navigation
[fix] NotificationDropdown panel has no focus management on open or close #1885
Description
File/location: frontend/src/app/components/global_ui/NotificationDropdown.tsx
Description:
The dropdown panel (role="dialog") never moves focus into itself when opened via the bell button, and none of its close paths (Escape key, outside click, the X button, or navigating to a notification) restore focus to the trigger button. Keyboard and screen-reader users lose their place in the page after every open/close cycle.
Acceptance Criteria:
- Opening the dropdown moves focus to the panel (or its first focusable element)
- Every close path (Escape, outside click, X button, item navigation) returns focus to the bell trigger button
- Automated a11y/keyboard test covers open, Escape-close, and outside-click-close focus behavior
Notes:
frontend/e2e/notifications-inbox.spec.ts's only real test is test.skip'd, so this has no active automated coverage either.
Filed via automated codebase sweep (frontend / fix).
Activity
shobhamerabacha-star commentedon Sep 28, 2026
Hello @maintainers,
I can tackle
[fix] NotificationDropdown panel has no focus management on open or close. Proposed implementation roadmap:LabsCrypt/remitlend[fix] NotificationDropdown panel has no focus management on open or closeinLabsCrypt/remitlendand apply a clean, surgical fix.Looking forward to collaborating on this—please assign!
Simultech369 commentedon Sep 28, 2026
Hello Maintainers!
Autonomous Council implementation and test verification for this issue has been completed, passing all test suites across 5 review surfaces, and submitted in PR #1934 (#1934).
Stellar Wave 9 Formalization & 1-Click Acceptance:
GABFQIK63R2NETJM7T673EAMZN4RJLLGP3OFUEJU5ZVTGWUKULZJNL60xEa3A353Fb3fc88DB8F0FA1E6Ea541FEdc9F5F0E7Maintainer Action: To credit this work for Wave 9 on Drips, please assign @Simultech369 to this issue or review and accept via the Drips Maintainer Portal:
Review / Accept on Drips Maintainer Dashboard
Thank you for your review!
janetobande commentedon Oct 21, 2026
@janetobande has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @janetobande to this issue.
amossamuel851-tech commentedon Oct 21, 2026
@amossamuel851-tech has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @amossamuel851-tech to this issue.
vijay11149 commentedon Oct 21, 2026
@vijay11149 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @vijay11149 to this issue.
Tamziycode commentedon Oct 21, 2026
@Tamziycode has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tamziycode to this issue.
Ghostcecode commentedon Oct 21, 2026
@Ghostcecode has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ghostcecode to this issue.
khaylebfortune commentedon Oct 21, 2026
@khaylebfortune has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @khaylebfortune to this issue.
Detayo07 commentedon Oct 21, 2026
@Detayo07 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Detayo07 to this issue.
drips-wave commentedon Oct 21, 2026
Congratulations, @khaylebfortune! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @khaylebfortune: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
grantfox-oss commentedon Oct 28, 2026
🎉 This issue has been marked as completed on GrantFox!
@khaylebfortune's PR #2181 was approved and merged by @K1NGD4VID.
🏆 @khaylebfortune: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (993 total points). Track your full progress on GrantFox.
👏 Great work, @khaylebfortune! Keep contributing to LabsCrypt.
drips-wave commentedon Oct 28, 2026
This issue has been marked as completed by a Drips Wave moderator for @khaylebfortune as part of the Stellar Wave Program's 10th Wave 🥳
Moderator's reason: [Auto-assessed] The PR #2181 was merged by maintainer @K1NGD4VID on 2026-10-28T14:11:58Z as evidenced by the merge timestamp and GrantFox notification, fully satisfying the issue completion requirements.
😎 @khaylebfortune: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.