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 #11924, comment 6

Timestamp:: May 12, 2014, 8:49:58 AM (11 years ago)
Author:: Catalin
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11924, comment 6

initial	v1
1	1	I think i get it now, so the old editor is still in the destroy process so that is why it's catching the custom config loaded event. If the destroy method would be completely finished, then the editor reference would not be there so it wouldn't catch the mention event. So i need to make sure the editor is finished destroying before proceeding. Is there any way to tell when this happened ? A specific event or someway to pass a handler ?
	2
	3	LE: oh wait, i can listen to the instanceDestroyed event. I think i know how to continue. Thanks for the help. Greatly appreciated :)