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

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #9953, comment 2

Timestamp:: Apr 5, 2013, 11:59:22 AM (11 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9953, comment 2

initial	v1
3	3	However, I can also think about different solution. Such non-editable container can be stored by reference and restored (the same element - not the same HTML) after data are set. However, I think that usual jQ gallery will blow up in such an environment. This is a hardcore scenario.
4	4
5		I confirm this as a new feature but at the same time I'm predicting that it's very unlikely to work on it. It's extremely complicated and at the same time can be achieved by placeholders implemented by widgets or fakeobjects.
	5	I confirm this as a new feature but at the same time I'm predicting that it's very unlikely that anyone will work on it. It's extremely complicated and at the same time can be achieved by placeholders implemented by widgets or fakeobjects.