DataViews: Move the rich text control into the editor package

[youknowriad]

What?

Closes #81233.

Moves the rich text control out of @wordpress/dataviews and into @wordpress/editor, next to the note form that is its only consumer. Removes the built-in richtext DataForm control (breaking) and DataViews' dependency on @wordpress/rich-text.

Why?

DataViews is a bundled package installed from npm, and the control unlocked @wordpress/rich-text at module scope — reachable from any import { DataForm }, via both the control registry and the privateApis export. Plugins importing @wordpress/dataviews crashed against the copy WordPress ships; the /wp build carried a second copy that reused core's core/rich-text store, so core's formats read the wrong React contexts and blanked the app. WooCommerce pinned 17.1.0, Jetpack patched around it.

Those were the only files importing rich-text, so moving them drops the dependency and both failure modes — lazy loading would only have covered the first. In @wordpress/editor, @wordpress/rich-text is the same wp.richText the block editor uses: one registry, one store, one set of contexts.

How?

The control, FormatEdit, getAllowedFormats, its tests and its placeholder styles move verbatim — only the wrapper class name and import paths changed. Gone from DataViews: the richtext registry entry, EditConfigRichText, the privateApis export (this control was its only member), @wordpress/rich-text, and the story field. The /wp build drops 122KB and every rich-text code path with it.

Two things to flag:

• Edit: 'richtext' was public API in 17.2, so DataViews needs a major bump. It only ever worked inside Gutenberg's own build.
• DataForm: Add a generalised richtext field #73180 is unsolved again for third parties: a rich text field still needs a custom Edit, and there's no public way to assemble one outside @wordpress/block-editor. That's the rich-text item in DataViews: remove all private API usage #81230 — this closes 6 of the others.

Testing Instructions

1. Open a post and add a note from the block options menu.
2. In the note field: ⌘B / ⌘I format, ⌘K opens the link popover and the field stays selected, `code` transforms, @ opens mentions, Shift+Enter makes exactly one new line, ⌘Enter submits.
3. Add a note, reply to it, edit it — formatting round-trips.

npm run test:e2e -- --project=chromium ../specs/editor/various/block-notes.spec.js passes 48/48, as do the unit tests for both packages.

Testing Instructions for Keyboard

Same as above — the whole flow is keyboard-driven.

Use of AI Tools

Authored with Claude Code (Opus 5): the move, the DataViews removals, the test runs, and this description.

[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: youknowriad <youknowriad@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: oandregal <oandregal@git.wordpress.org>

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

[github-actions]

Size Change: -5.2 kB (-0.07%)

Total Size: 7.65 MB

📦 View Changed

Filename	Size	Change
build/scripts/block-editor/index.min.js	434 kB	-1.48 kB (-0.34%)
build/scripts/edit-site/index.min.js	311 kB	-1.46 kB (-0.47%)
build/scripts/editor/index.min.js	510 kB	-512 B (-0.1%)
build/scripts/media-utils/index.min.js	129 kB	-1.55 kB (-1.18%)
build/styles/edit-site/style-rtl.css	21.6 kB	-42 B (-0.19%)
build/styles/edit-site/style-rtl.min.css	17.7 kB	-46 B (-0.26%)
build/styles/edit-site/style.css	21.6 kB	-43 B (-0.2%)
build/styles/edit-site/style.min.css	17.7 kB	-46 B (-0.26%)
build/styles/editor/style-rtl.min.css	27 kB	-7 B (-0.03%)
build/styles/editor/style.min.css	27 kB	-7 B (-0.03%)

_{compressed-size-action}

[Mamaduka]

Thanks, Riad!

Everything seems to works as before, and we have good e2e test coverage for the RichText notes feature.

[oandregal]

Thanks, this works for me.

We may want to offer richtext as a control like we offer textarea and others, but not by exporting it as private API.

[oandregal]

This PR seems important to backport to 7.1, so I've prepared #82186

[youknowriad]

Why should this be back ported to 7.1 branch?

[oandregal]

Actually, no need. DataViews isn't available through the global so nobody will have access to this change.