We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

Changes between Version 1 and Version 2 of Ticket #13334, comment 5

Timestamp:: Jun 12, 2015, 12:17:49 PM (9 years ago)
Author:: Szymon Cofalik
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #13334, comment 5

v1	v2
1		~~The method should find proper elements. Nested widgets are initialized during http://docs.ckeditor.com/#!/api/CKEDITOR.plugins.widget-method-initEditable~~ . As long as editables definitions and elements in DOM are in same order and you initialize only editables that are defined, everything should be fine.
	1	Since nested widgets are initialized during http://docs.ckeditor.com/#!/api/CKEDITOR.plugins.widget-method-initEditable the method should still find correct editables. As long as editables definitions and elements in DOM are in same order and you initialize only editables that are defined, everything should be fine.
2	2
3	3	To test this behavior I used widgetbootstrap plugin and edited two column widget adding extra editable without changing template.