Event system dies along with the last editor being destroyed

[Olek Nowodziński]

I stumbled upon this issue while developing sample for #11480.

This issue makes CKEditor events API quite useless without editor instance, especially if the editor is destroyed in the callback.

See ​jsFiddle.

---

How to reproduce?

1. Create editor instance.
2. Attach event listener on a DOM element outside of the editor. Not related to editable, etc.
3. See that event works.
4. Destroy the editor(s).

Actual:

5. Attached listener is not fired anymore.

Expected:

5. Attached listener is fired since the object in DOM is still there.

---

Quick research:

• ​https://github.com/ckeditor/ckeditor-dev/blob/master/core/dom/domobject.js#L150-L152
• #5663

[Piotrek Koszuliński]

cc

[Piotrek Koszuliński]

I find this very strange. I understand that it was done in order to free memory, but it's definitely a big negative surprise.

[Jakub Ś]

I was able to reproduce this issue from CKEditor 3.2.2 so perhaps there is something different that introduced this bug.