Compose Draft Save & Dismissal Behavior

Aperta
#259 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
frontend, web-dev

Direzione di ricerca

Start by locating the Compose window and its close or dismissal handling in the TypeScript app. Compare the current Save or Discard prompt with the proposed behavior of saving edits to Drafts on close; the issue also suggests a Delete action and an Undo snackbar. Confirm the intended interaction with maintainers before implementation, then verify that closing a dirty Compose window saves the draft and offers a clear recovery path.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

ux

Describe the bug

Every time a user closes a dirty Compose window, they are prompted to confirm whether they want to save or discard the message to assist in determining the route for the message storage. However, this introduces unnecessary friction into an otherwise expected action: closing a window.

To Reproduce

Steps to reproduce the behavior:

  1. Go to Compose window
  2. Edit the message
  3. Click the Close X button
  4. Observe a small dropdown menu asking to confirm Save or Discard.

Recommendation

* Consider adding a Delete button to the bottom of the Compose window to provide an explicit discard action. 
* Consider updating so closing a modified Compose window would automatically save changes and move to Drafts, eliminating the need for a confirmation dialog. 
* We have a design task in process for confirmation snackbars with Undo buttons when messages move to another folder and it would also make sense to show the Moved to Drafts folder toast with an Undo button as a method of passive confirmation with recovery for the move.
image

Tradeoffs

We discussed the tradeoff between the repeated friction of a confirmation dialog and the potential accumulation of abandoned drafts. We briefly touched on automatic cleanup in Deleted Items after a defined period of inactivity. However, time-based deletion aligns more naturally with the Deleted Items folder than with Drafts, where users may intentionally keep unfinished messages for extended periods.

System

OS: macOS Golden Gate 27.2
Browser Version: Firefox 160.0 (aarch64)

Lingua principale
TypeScript
Stelle
121
Fork
11
Merge medio
1g 3h
PR unite (30g)
11

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di thunderbird/stormbox

Tutte le issue di thunderbird/stormbox

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.