Rich Text: Restore the selection when focus returns to the editable

[Mamaduka]

What?

Part of #80294.

PR removes domOnly: true from the rich text focus handler, so focus restores the record's selection again.

Why?

Select text in a same-document rich text field, press Cmd+K, then press Escape. The caret returns to the start of the text instead of the selection.

The field and the link popover share one document, so focusing the popover's input takes the document's only selection. domOnly: true makes the focus handler skip applySelection, so nothing restores it. An iframed editor is unaffected; its canvas is a separate document with its own selection, which is why this only surfaces in same-document fields: the non-iframed block editor (widgets screen) and the dataviews RichTextControl (block notes).

domOnly: true came from #58745, fixing #58322 (clicking between two links in a paragraph opened the wrong preview). It has been vestigial since #59635 (March 2024) added shouldAutoFocus, which stops the Link UI from stealing focus on link-click. That removed the focus round-trip #58322 depended on, so the focus handler is no longer on that path: it receives zero focusin events in the #58322 scenario, and #58322's e2e guard passes with or without domOnly.

Testing Instructions

1. Add a note to a block (or use the widgets screen).
2. Type some text and select it.
3. Press Cmd+K to open the link UI, then press Escape.
4. The text should still be selected, not collapsed to the start.

Automated: new e2e covering this in block-notes.spec.js. links.spec.js (incl. the #58322 guard), rich-text.spec.js, writing-flow.spec.js and block-notes.spec.js show no new failures.

Testing Instructions for Keyboard

Same.

Screenshots or screencast

CleanShot.2026-07-17.at.11.25.03.mp4

CleanShot.2026-07-17.at.11.28.47.mp4

Use of AI Tools

Assisted by Claude.

[github-actions]

Size Change: -2 B (0%)

Total Size: 7.73 MB

📦 View Changed

Filename	Size	Change
build/scripts/rich-text/index.min.js	14.8 kB	-2 B (-0.01%)

_{compressed-size-action}

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
Co-authored-by: noruzzamans <noruzzaman@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[noruzzamans]

Tested on trunk, where the issue was reproduced, and on the fix/rich-text-control-focus-return branch, where the selection was restored correctly and no regressions were found.

Screen.Recording.2026-07-17.at.2.56.50.PM.mov

[ellatrix]

Seems ok.

[github-actions]

I just cherry-picked this PR to the wp/7.1 branch to get it included in the next release: db43dd2

[t-hamano]

I just cherry-picked this PR to the release/23.6 branch to get it included in the next release: 3bbc5dc