fix(search): activate search-bar buttons from the keyboard

The next/previous/close/replace buttons listened only to pointerdown,
while Enter/Space on a focused native button fires click. Handle
keyboard-initiated clicks (detail === 0) without changing the pointer
path.

Fixes #1440

Author: xdan

CHANGELOG.md

@@ -9,6 +9,12 @@
 > - :house: [Internal]
 > - :nail_care: [Polish]
 
+## 4.13.20
+
+#### :bug: Bug Fix
+
+- **Search**: the next/previous/close/replace buttons of the search bar could be reached with Tab but did nothing on Enter/Space — the handlers listened only to `pointerdown`, while keyboard activation of a native button fires `click`. Keyboard-initiated clicks (`detail === 0`, which also covers screen readers) are now handled; pointer behaviour is unchanged. Fixes [#1440](https://github.com/xdan/jodit/issues/1440).
+
 ## 4.13.19
 
 #### :bug: Bug Fix

src/plugins/search/search.test.js

@@ -631,6 +631,43 @@ describe('Search plugin', () => {
 			});
 		});
 
+		describe('Keyboard activation of the search buttons', () => {
+			// Activating a focused native button with Enter/Space fires a
+			// `click` with `detail === 0` (there is no `pointerdown`)
+			// https://github.com/xdan/jodit/issues/1440
+			it('Should search next and close on a keyboard click', async () => {
+				const editor = getJodit({
+					defaultTimeout: 0,
+					search: {
+						useCustomHighlightAPI: false
+					}
+				});
+
+				editor.value = '<p>test</p>';
+
+				clickTrigger('find', editor);
+				clickButton('find', getOpenedPopup(editor));
+
+				await editor.async.requestIdlePromise();
+				const inputs = getSearchInputs(editor);
+				inputs.query.value = 't';
+
+				simulateEvent('click', inputs.nextButton);
+				await editor.async.requestIdlePromise();
+
+				expect(sortAttributes(editor.getNativeEditorValue())).equals(
+					'<p><span data-jodit-temp="true" jd-tmp-selection="true">t</span>es<span data-jodit-temp="true" jd-tmp-selection="true">t</span></p>'
+				);
+
+				simulateEvent('click', inputs.closeButton);
+				await editor.async.requestIdlePromise();
+
+				expect(editor.getNativeEditorValue()).equals('<p>test</p>');
+				expect(editor.container.querySelector('.jodit-ui-search')).is
+					.null;
+			});
+		});
+
 		describe('After close', () => {
 			let editor, search, inputs;
 

src/plugins/search/ui/search.ts

@@ -106,11 +106,33 @@ export class UISearch extends UIElement<IJodit> {
 		this.currentBox = current as HTMLSpanElement;
 		this.countBox = count as HTMLSpanElement;
 
+		const closeAction = (): void => this.close();
+		const replaceAction = (): void =>
+			void jodit.e.fire(this, 'pressReplaceButton');
+		const nextAction = (): void => void jodit.e.fire('searchNext');
+		const prevAction = (): void => void jodit.e.fire('searchPrevious');
+
+		// Pointer activation is handled on `pointerdown` (returning `false`
+		// there keeps the focus and selection intact), but activating a
+		// native button from the keyboard (Enter/Space) fires only `click`
+		// with `detail === 0` — handle that path separately. Pointer clicks
+		// arrive with `detail >= 1`, so the action does not run twice.
+		// See https://github.com/xdan/jodit/issues/1440
+		const onKeyboardActivate =
+			(action: () => void) =>
+			(e: MouseEvent): void => {
+				if (!e.detail) {
+					e.preventDefault();
+					action();
+				}
+			};
+
 		jodit.e
-			.on(this.closeButton, 'pointerdown', () => {
-				this.close();
+			.on(this.closeButton, 'pointerdown', (): false => {
+				closeAction();
 				return false;
 			})
+			.on(this.closeButton, 'click', onKeyboardActivate(closeAction))
 			.on(this.queryInput, 'input', () => {
 				this.currentIndex = 0;
 			})
@@ -120,18 +142,21 @@ export class UISearch extends UIElement<IJodit> {
 					this.selInfo = jodit.s.save();
 				}
 			})
-			.on(this.replaceButton, 'pointerdown', () => {
-				jodit.e.fire(this, 'pressReplaceButton');
+			.on(this.replaceButton, 'pointerdown', (): false => {
+				replaceAction();
 				return false;
 			})
+			.on(this.replaceButton, 'click', onKeyboardActivate(replaceAction))
 			.on(next, 'pointerdown', (): false => {
-				void jodit.e.fire('searchNext');
+				nextAction();
 				return false;
 			})
+			.on(next, 'click', onKeyboardActivate(nextAction))
 			.on(prev, 'pointerdown', (): false => {
-				jodit.e.fire('searchPrevious');
+				prevAction();
 				return false;
 			})
+			.on(prev, 'click', onKeyboardActivate(prevAction))
 			.on(this.queryInput, 'input', () => {
 				this.setMod('empty-query', !trim(this.queryInput.value).length);
 			})