How a confirmation dialog resolves when it is auto-resolved via autoResolve,
i.e. skipped and answered programmatically instead of shown to the user.
'accept' — perform the dialog's affirmative/primary action without
showing the prompt.
'reject' — take the dialog's safe, non-destructive branch without
showing the prompt (cancel/dismiss — never discard or delete).
'accept'/'reject' name the answer to the dialog, not the literal button
labels, so 'reject' is uniformly safe across every dialog and a blanket
"reject everything" can never silently lose work. Per slot:
Slot
'accept'
'reject'
annotations.deleteConfirm
delete the annotation
keep it
contentEditor.exitConfirm
save & exit
keep editing (do not discard)
contentEditor.downloadConfirm
download & continue
dismiss without downloading
reloadConfirm
reload the document
keep the current document
The only destructive outcome that is deliberately not reachable through
autoResolve is discarding unsaved content-editor work; do that explicitly
via getInstance()?.discardContentEditingSession().
How a confirmation dialog resolves when it is auto-resolved via
autoResolve, i.e. skipped and answered programmatically instead of shown to the user.'accept'— perform the dialog's affirmative/primary action without showing the prompt.'reject'— take the dialog's safe, non-destructive branch without showing the prompt (cancel/dismiss — never discard or delete).'accept'/'reject'name the answer to the dialog, not the literal button labels, so'reject'is uniformly safe across every dialog and a blanket "reject everything" can never silently lose work. Per slot:'accept''reject'annotations.deleteConfirmcontentEditor.exitConfirmcontentEditor.downloadConfirmreloadConfirmThe only destructive outcome that is deliberately not reachable through
autoResolveis discarding unsaved content-editor work; do that explicitly viagetInstance()?.discardContentEditingSession().