Improve responsiveness composing mails with large inline attachments
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by locating the compose editor code that handles pasted images and converts them into data URLs. Check how draft saving and image cleanup work, then verify that large inline images keep the composer responsive and remain usable before the first draft save without requiring a server upload.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
When pasting an image in to a mail we store it in the <img> src attribute as a data URL.
`<img src="data:image/png;base64,iVBO...`
This causes the browser to struggle with staying response. The larger the file size the inline image is the more apparent it becomes.
Describe the solution you'd like
Use blob URLs instead.
Describe alternatives you've considered
Uploading the inline images directly to the server and the using the ULRs to the uploaded files.
Using uploaded images is a good solution once the composed data was save as draft.
Until first save as draft blob URL work without requiring a server to upload the images.
Additional context
No response
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 363
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 80
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 nextcloud/mail
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nextcloud/mail#13841 · 1 comment ·
Maintainers usually reply within 1 day
-
0. to triage enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Show email next to name in Search dropdownPossibly taken @vansh-nagar claimed this 17 days ago. Open1. to develop enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nextcloud/mail#13703 · 1 comment ·
Maintainers usually reply within 1 day
-
ISO-2022-JP emails are garbled in Mail 5.10.12 [Minimal fix available]Possibly taken @neconohitomi claimed this 37 days ago. Open1. to develop bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
nextcloud/mail#13472 · 1 comment ·
Maintainers usually reply within 1 day
-
1. to develop technical debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
holepunchto/hrpc-test#28 ·
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
anoopcodehack/DevBoard#616 ·
Maintainers usually reply within 2 days
-
idnits3
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
ietf-tools/idnits#319 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
521xueweihan/HelloGitHub#3939 ·