1 parent
5dc9db0b1c
commit
83440f20e2
28 files changed
+1925
-213
No files matched your search
@@ -1,5 +1,43 @@
|
||||
# RustBox changelog
|
||||
|
||||
### 0.2.12
|
||||
|
||||
- Saving or updating a draft no longer raises a realtime “new message” toast/system notification for the Drafts folder; the folder/list still refreshes normally, and IMAP snapshots remain `\Draft` + `\Seen`.
|
||||
- Added a composer `Delete draft` action that permanently removes the current IMAP draft and cascades cleanup through the local autosave row, draft attachment rows and uploaded attachment blobs; IMAP deletion is verified before local state is reported as deleted.
|
||||
- IMAP-only drafts opened from other mail clients can be deleted without requiring a pre-existing RustBox draft database row, while UIDVALIDITY and `\\Draft`/Drafts-folder checks prevent deleting a stale or non-draft message by mistake.
|
||||
- Explicit `Save draft` now records the newly appended IMAP UID in the live composer even for a brand-new draft, so later Save/Delete/Send operations consistently target the current server snapshot.
|
||||
- Draft messages in the configured IMAP Drafts folder (or carrying the `\\Draft` flag) now open directly in the normal composer from their server-side RFC822/MIME content; opening does not depend on a RustBox draft database row or `X-RustBox-Draft-ID`, so drafts created by other mail clients can be edited and sent.
|
||||
- Editing an IMAP-sourced draft keeps its original server UID as the replacement source: explicit Save draft appends the new MIME snapshot first and removes the superseded IMAP draft only after the new UID is resolved; sending also removes the source draft after successful SMTP delivery.
|
||||
- Existing IMAP draft attachments stay usable directly from their MIME parts while editing, can be removed/re-embedded without first copying the whole message into the draft database, and are carried into Save/Send together with newly uploaded local attachments.
|
||||
- Inline MIME parts now preserve their original filenames through `Content-Disposition: inline; filename=...` when saving drafts and sending messages, improving Roundcube/Thunderbird interoperability.
|
||||
- IMAP draft reopening restores To/Cc/Bcc, Subject, plain/HTML body, reply threading headers, priority, MDN state, From identity when it matches a configured identity, inline CIDs and attachment filenames directly from the server message.
|
||||
- Fixed manual IMAP draft saving for drafts without To/Cc/Bcc recipients by using a build-only envelope while keeping recipient headers empty; Bcc is retained in saved draft snapshots.
|
||||
- IMAP draft saving now honors the per-account Special folders → Drafts mapping and `default_drafts_folder`, then falls back to the IMAP `\Drafts` attribute and common `Drafts`/`Draft` folder names.
|
||||
- Added an explicit `Save draft` composer action immediately before `Cancel`; it forces the current message and attachments to be persisted as a real IMAP `\Draft` snapshot while leaving background autosave behavior unchanged.
|
||||
- Manual IMAP draft saves now report a failure when RFC822 snapshot creation or IMAP APPEND fails instead of showing a misleading success state.
|
||||
- Fixed draft recovery so attachment metadata is restored from both the browser recovery snapshot and the authoritative server draft.
|
||||
- Composer attachment chips now show every uploaded file, including inline images/links, instead of hiding embedded items from the attachment list.
|
||||
- Adding another attachment now merges by unique attachment ID and refreshes the server-side draft attachment list, preventing an existing chip from appearing to be replaced.
|
||||
- Inline attachment chips expose an attachment-only action that removes the inline occurrence without deleting the uploaded file.
|
||||
- Stretched `Load more` and `Load all` across the full message-list action area with equal-width controls.
|
||||
- Added a composer `Hide fields` / `Show fields` toggle that collapses From/To/Cc/Bcc/Subject/options so the editor can use the freed vertical space; invalid recipient input automatically expands the fields again.
|
||||
- Fixed inline image insertion so adding another image or attachment appends a new element instead of replacing the current selection.
|
||||
- Replaced deprecated `execCommand("insertHTML")` attachment insertion with DOM Range insertion and safe caret placement.
|
||||
- Removed filename/size attachment de-duplication so separate files with identical metadata can still be attached independently.
|
||||
- Moved inline-image resize/alignment controls into a floating contextual panel so selecting an image no longer reduces the composer editing area.
|
||||
- Added mouse/touch resize handles around the selected inline image while preserving its aspect ratio.
|
||||
- Inline images can be dragged to another caret position inside the message body.
|
||||
- Pasting PNG/JPEG/GIF/WebP files with Ctrl/Cmd+V embeds them inline, and dropping files into the editor uploads them at the drop position.
|
||||
- Attachment chips explicitly identify regular/image attachments, while selected embedded images are labelled `Inline image`.
|
||||
- Made attachment re-embed actions compact icon buttons to keep the attachment strip readable.
|
||||
- Collapsed large To/Cc recipient lists in the message reader into a compact summary with on-demand expansion.
|
||||
- Added a `Load all` action beside `Load more` in the message list.
|
||||
- Renamed the reader toolbar action from `Message details` to `Details`.
|
||||
- Images added to HTML messages now embed inline by default; removing an inline image keeps the underlying file available as an attachment that can be embedded again.
|
||||
- Added `Embed` actions for attachments: images are inserted inline and other files can be inserted as CID links in the message body.
|
||||
- Added quick inline-image sizing and alignment controls, plus the existing advanced crop/resize editor and an explicit `Keep as attachment` action.
|
||||
- No schema migration is required; V049 remains the next migration number.
|
||||
|
||||
### 0.2.11
|
||||
|
||||
- No schema migration is required; V049 remains the next migration number.
|
||||
|
||||
Reference in new issue
Block a user