From e1ddc65f85f0d426c84970ef25e8a8af299ae454 Mon Sep 17 00:00:00 2001 From: r-zakarya <82443831+r-zakarya@users.noreply.github.com> Date: Wed, 22 Jul 2026 23:33:52 +0100 Subject: [PATCH] fix(editor): batch-bar clicks no longer dismiss the editor MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The click-outside handler whitelists chrome (topbar, sidebar, pagination…) but not .batch-bar, so Delete / Clear / Move to folder / Add tag counted as an outside click and ran requestCloseSlideOver before their own handler. Whitelist it, plus .content-header which carries buttons of its own (Empty trash). Those actions now decide for themselves what happens to the editor via closeEditorForDeleted. Co-Authored-By: Claude Opus 4.8 --- js/app.js | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/js/app.js b/js/app.js index b4f5d92..2272c14 100644 --- a/js/app.js +++ b/js/app.js @@ -7275,6 +7275,11 @@ async function init() { if (e.target.closest('.topbar')) return; if (e.target.closest('.sidebar')) return; if (e.target.closest('.pagination')) return; + // Selection toolbar + the view's title row (which carries buttons + // like Empty trash) are chrome as well — their actions decide for + // themselves what happens to the editor. + if (e.target.closest('.batch-bar')) return; + if (e.target.closest('.content-header')) return; if (e.target.closest('.cols-menu')) return; if (e.target.closest('.filters-menu')) return; if (e.target.closest('.user-menu')) return;