-
-
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
Introduce EditorUI#update event #2890
Closed
Labels
package:core
type:feature
This issue reports a feature request (an idea for a new functionality or a missing option).
Milestone
Comments
oleq
referenced
this issue
in ckeditor/ckeditor5-core
Jun 29, 2018
Feature: Introduced the `EditorUI#update` event. Closes #130. BREAKING CHANGE: The `EditorUI` is now a class (no longer an interface).
oleq
referenced
this issue
in ckeditor/ckeditor5-editor-classic
Jun 29, 2018
Other: Used the `EditorUI` as a parent class for the `ClassicEditorUI` (see ckeditor/ckeditor5-core#130).
oleq
referenced
this issue
in ckeditor/ckeditor5-editor-inline
Jun 29, 2018
Other: Used the `EditorUI` as a parent class for the `InlineEditorUI` (see ckeditor/ckeditor5-core#130).
oleq
referenced
this issue
in ckeditor/ckeditor5-editor-balloon
Jun 29, 2018
Other: Used the `EditorUI` as a parent class for the `BalloonEditorUI` (see ckeditor/ckeditor5-core#130).
oleq
referenced
this issue
in ckeditor/ckeditor5-editor-decoupled
Jun 29, 2018
Other: Used the `EditorUI` as a parent class for the `DecoupledEditorUI` (see ckeditor/ckeditor5-core#130).
oleq
referenced
this issue
in ckeditor/ckeditor5-link
Jun 29, 2018
Internal: Used the `EditorUI#update` event instead of `View#render` to attach the UI components (see ckeditor/ckeditor5-core#130).
oleq
referenced
this issue
in ckeditor/ckeditor5-table
Jun 29, 2018
Internal: Used the `EditorUI#update` event instead of `View#render` to attach the UI components (see ckeditor/ckeditor5-core#130).
oleq
referenced
this issue
in ckeditor/ckeditor5-ui
Jun 29, 2018
Internal: Used the `EditorUI#update` event instead of `View#render` to attach the UI components (see ckeditor/ckeditor5-core#130).
oleq
referenced
this issue
in ckeditor/ckeditor5-image
Jun 29, 2018
Fix: The UI should update once the image is loaded. Closes #142. Used the `EditorUI#update` event instead of `View#render` to attach the UI components (see ckeditor/ckeditor5-core#130).
mlewand
added
status:confirmed
type:feature
This issue reports a feature request (an idea for a new functionality or a missing option).
package:core
labels
Oct 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
package:core
type:feature
This issue reports a feature request (an idea for a new functionality or a missing option).
Now we use
view#render
event to attach and reposition floating UI stuff. The problem is that rendered layout should not be the only reposition trigger. We are going to introduceViewDocument#layoutChanged
event https://github.com/ckeditor/ckeditor5-engine/issues/1445 so we will have another trigger soon. Besides, we should make it possible to trigger UI refresh manually without touching the engine part.We decided to introduced one
EditorUI#update
event. This event should be fired every time when editor UI should be refreshed (after all document layout changes). All UI part of the plugins should listen to this event instead ofview#render
.Related stuff:
The text was updated successfully, but these errors were encountered: