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 #11131, comment 5

Timestamp:: Dec 30, 2013, 9:44:25 AM (10 years ago)
Author:: Marek Lewandowski
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11131, comment 5

initial	v1
1		Fix for this issue is already prepared, however we still need to prepare TCs for that issue ( ~~contentDomUnload event firing in each wysiwyg mode ) - for that i'll wait for PJ tests modifications~~, which will run given test in each wysiwyg mode.
	1	Fix for this issue is already prepared, however we still need to prepare TCs for that issue ( ensuring that contentDomUnload event fires in each wysiwyg mode ) - for that i'll wait for PJ tests modifications in #5217, which will run given test in each wysiwyg mode.