We are planning our migration from D9 to D10 and with it the move also from CKE4 to CKE5.
Previously we have installed the
ckeditor_config →
plugin and are using the fullPage=true to save < html > to < /html > contents using CKE4. From the documentation of CKE5, the FullPage html-support preserves those tags but from what I've read the CKE5 from D10 core only supports GHS html-support. Will introducing the FullPage html-support as a plugin work with the current core CKE5? Or would it need to be a separate CKE5 build and introduced as a new editor option via contrib module?
1. Fresh install of D10
2. Create content
3. In the CKE5 enabled editor body, click on Source
4. Input a sample < html > to < /html > page
5. Save the content
6. Verify in node_revision_body that the tags are preserved
NA
NA
NA
NA
NA
NA
Needs review
10.1 ✨
Last updated
It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).
IMHO this does not belong in Drupal core.
But in the end it's a product manager decision. So assigning to them.