Opening composer modal causes console error
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Open the app
- Composer a message
- Send it
- Click Undo on the toast
Expected behavior
No error
Actual behavior
Uncaught (in promise) TypeError: el is null
getCandidates index.esm.js:76
tabbable index.esm.js:530
containerGroups focus-trap.esm.js:333
updateTabbableNodes focus-trap.esm.js:332
activate focus-trap.esm.js:863
useFocusTrap NcModal.mjs:530
mounted NcModal.mjs:370
VueJS 20
set pinia.mjs:926
startComposerSessionMutation actions.js:1857
wrappedAction pinia.mjs:1399
actionName pinia.mjs:932
startComposerSession actions.js:495
handleHttpAuthErrors sessionExpiryHandler.js:11
startComposerSession actions.js:367
wrappedAction pinia.mjs:1399
actionName pinia.mjs:932
sendMessageWithUndo outboxStore.js:248
node_modules mail.js:5395
showUndo _plugin-vue2_normalizer-CQ6iBklL.mjs:121
sendMessageWithUndo outboxStore.js:233
sendMessageWithUndo outboxStore.js:231
wrappedAction pinia.mjs:1399
actionName pinia.mjs:932
onSend NewMessageModal.vue:333
invokeWithErrorHandling VueJS
The rest seems to work
Mail app version
4.3
Nextcloud version
No response
Mailserver or service
No response
Operating system
No response
PHP engine version
None
Nextcloud memory caching
No response
Web server
None
Database
None
Additional info
No response
Contributor 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.
Research direction
Reproduce the flow in Mail app 4.3: send a message, click Undo, and observe the focus-trap error. Start with NewMessageModal.vue around onSend, then trace sendMessageWithUndo in outboxStore.js and startComposerSession in actions.js; done means the Undo flow completes without the reported console error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100