-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confusing behavior of CKEditor 5 when launching the editor on a <textarea> element #1591
Comments
Related issues:
Also, I'd remove all mentions of |
@wwalc, I know that it's you in https://stackoverflow.com/questions/55142625/creating-decouplededitor-passing-textarea-as-parameter :D I don't believe in such coincidences ;) |
Other: Introduce editor-wrong-element error thrown when editor is created over wrong element. Closes ckeditor/ckeditor5#1591.
Reached here with a google search. So CKEditor5 won't support if used with <textarea> tag is it? |
There are several places where we show an example of Classic editor being launched on top of a
<textarea>
element:If someone takes such an example and later tries to change the editor type (e.g. the Balloon editor), then will see that the editor no longer shows up:
Result in a browser:
Expected result
BalloonEditor.create() documentation could mention if there are any limitations on what can be passed as
sourceElementOrData
argument.The editor could log some meaningful error into the console when unsupported element is passed.
The text was updated successfully, but these errors were encountered: