-
-
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
Placeholder does not disappear after inserting media #1684
Closed
pomek opened this issue
Apr 5, 2019
· 1 comment
· Fixed by #7621 · May be fixed by ckeditor/ckeditor5-engine#1749
Closed
Placeholder does not disappear after inserting media #1684
pomek opened this issue
Apr 5, 2019
· 1 comment
· Fixed by #7621 · May be fixed by ckeditor/ckeditor5-engine#1749
Labels
type:bug
This issue reports a buggy (incorrect) behavior.
Milestone
Comments
Related #4114. |
Reinmar
added a commit
that referenced
this issue
Jul 22, 2020
Feature (engine): Implemented the view `RawElement`. Implemented the `DowncastWriter#createRawElement()` method. Closes #4469. Fix (media-embed): The editor placeholder should disappear after inserting media into an empty editor. Closes #1684. Docs (ckeditor5): Used the `RawElement` instead of `UIElement` in the "Using a React component in a block widget" guide (see #1684). Internal (media-embed): Removed the `getFillerOffset()` hack from the `createMediaFigureElement()` helper that is no longer needed since the media content is rendered using `RawElements` (see #1684). BREAKING CHANGE (engine): The `DomConverter#getParentUIElement()` method was renamed to `DomConverter#getHostViewElement()` because now it supports both `UIElement` and `RawElement` (see #4469).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a bug report or feature request? (choose one)
🐞 Bug report
💻 Version of CKEditor
Master and the latest release.
📋 Steps to reproduce
✅ Expected result
Type the content here!
should disappear.❎ Actual result
But it does not:
📃 Other details that might be useful
I can reproduce it on Firefox, Chrome, and Safari.
The text was updated successfully, but these errors were encountered: