-
-
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
Remove config.image.defaultToolbar #5070
Labels
package:image
type:task
This issue reports a chore (non-production change) and other types of "todos".
Milestone
Comments
https://github.com/ckeditor/ckeditor5-image/issues/64#issuecomment-283079934 Let's not forget that the in all our samples and everywhere the toolbar should be configured as |
Reinmar
referenced
this issue
in CKEditor5/ckeditor5.github.io
Apr 20, 2017
Reinmar
referenced
this issue
in ckeditor/ckeditor5-build-classic
Apr 20, 2017
I changed the order of buttons in the classic build (ckeditor/ckeditor5-build-classic@131cbe7) and on https://ckeditor5.github.io (CKEditor5/ckeditor5.github.io@ff4ffcf). What remains here is getting rid of |
oleq
referenced
this issue
in ckeditor/ckeditor5-image
Apr 24, 2017
Reinmar
referenced
this issue
in ckeditor/ckeditor5-image
Apr 24, 2017
Other: Removed automatically filled `config.image.defaultToolbar`. Now, when initializing editor one must always define `config.image.toolbar`. Closes #60. BREAKING CHANGE: The `config.image.defaultToolbar` is no longer available. All editor instances must configure `config.image.toolbar` instead.
mlewand
added
status:confirmed
type:task
This issue reports a chore (non-production change) and other types of "todos".
package:image
labels
Oct 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
package:image
type:task
This issue reports a chore (non-production change) and other types of "todos".
As explained in https://github.com/ckeditor/ckeditor5-ui/issues/155#issuecomment-282300881.
For now, we're going to require that you specify the config. We'll create a system to pre-configure this by features in the future (see #409).
The text was updated successfully, but these errors were encountered: