CKEditor 5 #6249
Draft
CKEditor 5 #6249
+44
−17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
NOTE: Requires changes found in #6248 in order to work correctly. |
|
Do you want to merge this into master for eventual release in 2.1? That way people could start testing it more easily? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref #6209
This uses CKEditor 5 "Classic Mode", which turns a textarea field into an in-browser editor field.
This implementation "appears" initially to work, but I haven't tested whether there are features lost by making the change, nor any frustrations that end-users might encounter by using it with Classic mode defaults and no plugins.
Feedback requested because extensive testing is needed, lest content gets accidentally lost or formatting gets messed up because of settings or oversights.