Closed (fixed)
Project:
Drupal core
Version:
main
Component:
ckeditor5.module
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Apr 2026 at 16:53 UTC
Updated:
20 May 2026 at 07:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
longwaveCKEditor5 v48.0.0 no longer supports the DLL installation method: https://github.com/ckeditor/ckeditor5/releases/tag/v48.0.0
That means this issue is postponed on #3527914: Use UMD installation method for CKEditor5
Please note also that this is unlikely to land in Drupal 11; per our agreement with CKSource we intend to stay on the LTS v47 version of CKEditor5 in Drupal 11.
Comment #3
longwaveComment #4
joseph.olstadOk, gotcha, thats fine since we have the ckeditor5_table_fix module that will get us through until then.
Now we know what to expect! Sounds good!
Comment #5
godotislate#3527914: Use UMD installation method for CKEditor5 is in, so we can go ahead for D12 (only).
Comment #6
andrew.wang commentedAdded more linked issues that upgrading to v48 can resolve.
Comment #7
andrew.wang commentedRe-formatted issue summary with nested lists.
Comment #8
longwaveComment #10
godotislateOne comment on the MR.
Also, we haven't done #3551053: Remove jsdoc integration for CKEditor5, but I wonder if the script even works anymore with the new build.
Comment #11
longwaveUpdated the deprecated versions, I think we should keep them in sync.
yarn vendor-updateno longer updates them for us, so did it manually withsed.The jsdoc script doesn't work, it just deletes all entries in the file, so I left that alone for that other issue.
Comment #12
longwaveFixed the jsdoc script, the glob and regex just need updating a tiny bit to look at the TypeScript definitions. I closed #3551053: Remove jsdoc integration for CKEditor5.
Comment #13
godotislateComments all addressed, lgtm.
Comment #14
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #15
godotislateI rebased to make sure, but a test failure persist:
The cron one seems to be intermittent.
Comment #16
godotislateI fixed the test byte numbers in AssetAggregationAcrossPagesTest. Since this was RTBC before, and everything since is merge conflict resolution or performance test tweaks, I'm going to put this back to RTBC.
Comment #17
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #18
godotislateSilencing the bot because it's flagging a bunch of false eslint issues like:
Comment #19
catchCommitted/pushed to main, thanks!