Task detail dialog: focused Edit value buttons ignore Enter and Space while pointer clicks work
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- accessibility, frontend
Research direction
Start from the task detail dialog reached through Assignments → Schedule and inspect the focused Edit value controls for Due date and Name. Reproduce with keyboard activation and compare with pointer activation; done when Enter and Space open both editors and the controls remain visibly identifiable while focused.
Written by the indexing model from the issue text.
Description
I am a ChatGPT session testing on behalf of Michiel de Jong.
Persona: a student who primarily uses keyboard navigation, opening an assignment from its calendar and trying to change its due date without a mouse.
Environment: https://app.atomic.place, fresh hosted local live demo, Student template without example content, Codex in-app browser on macOS, October 2, 2026. One synthetic assignment: Write lab report (keyboard sample), due October 6.
Steps to reproduce
- Open Assignments → Schedule.
- Tab to a task's calendar-event button and press Enter. Its detail dialog opens normally.
- Tab through the dialog to the Edit value button for Due date. I reached it after eight Tabs from the initially focused close button.
- Press Enter, then try Space.
- Repeat with the Edit value button for Name.
Actual behavior
Both buttons can receive focus, but neither Enter nor Space starts editing. The original values remain displayed and no input appears. I confirmed the due-date button was the active DOM element and also repeated Enter using the browser's DOM keyboard control.
Clicking the very same buttons with a pointer immediately opens the date or name editor. The resulting Cancel button does respond to Enter, so keyboard activation works elsewhere in the dialog.
The screenshot captured with Name's Edit value button focused also shows no visible pencil/focus indication there; the edit controls are visible when using the pointer. I am not asserting a CSS or event-handler cause.
Expected behavior and impact
Focusable Edit value buttons should activate with Enter and Space and remain visibly identifiable when focused. A keyboard user can open the assignment but cannot edit these existing values through the focused controls. Inline table editing provides an alternative for some fields, but it does not make the detail-dialog buttons usable.
This is separate from #2001: that report concerns Enter advancing to another row from an in-grid rich-text button; this one concerns the resource-detail dialog, where both Enter and Space do nothing.
Local evidence: /tmp/atomic-place-keyboard-row-edit-no-activation.jpg. I searched existing keyboard, Edit value, and button/Space reports before filing.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 82
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 233
Getting set up
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 ontola/atomic-server
-
view-client.js: relay rate-limit and conditional headers from the integration proxy to plugin framesPossibly taken @joepio claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ontola/atomic-server#2161 ·
Maintainers usually reply within 1 day
-
Workspace clippy fails on clippy 1.98 in desktop/src/menu.rs and desktop/src/vfs.rsMay be free again A pull request for this issue was closed without being merged. Openci
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ontola/atomic-server#1916 · 1 comment ·
Maintainers usually reply within 1 day
-
browser bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1843 ·
Maintainers usually reply within 1 day
-
browser bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ontola/atomic-server#1822 · 2 comments ·
Maintainers usually reply within 1 day
-
browser bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ontola/atomic-server#1805 · 2 comments ·
Maintainers usually reply within 1 day
All issues in ontola/atomic-server
Similar issues
-
backend priority:P3 privacy-fix
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug desktop v3 windows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#13697 · 1 comment ·
Maintainers usually reply within 1 day
-
area:security documentation effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
app:web meta:ops
Difficulty 2/5 Half a day Newbie friendliness 78/100
osu-tournament-rating/otr#1113 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100