editor.destroy() does not cleanup content generated by TableResize plugin for inline editors

[Teresa Monahan]

To Reproduce:

• Copy inline_destroy.html (attached) into a build where the tableresize plugin is available and open it in a browser.
• Click inside the editor and resize a table column (or hover over the column boundaries so that the resizer icon is displayed).
• Inspect the HTML for the page and see that the tableresize plugin has added an element, e.g.

{{{<div contenteditable="false" style="position: absolute; cursor: col-resize; opacity: 0; padding: 0px; background-color: rgb(0, 0, 68); background-image: none; border: 0px none; z-index: 10; width: 3px; height: 49px; left: 272px; top: 213.867px; display: none;" unselectable="on" data-cke-temp="1"></div> }}}

• Click the 'Destroy Editor' button.
  

Problem: Inspect the HTML for the page again and see that the element added by the tableresize plugin is still present.

If you then click the 'Create Inline Editor' button to recreate the editor, and resize a table column again, the tableresize plugin adds a new element to the DOM. The old element is redundant and should be removed from the DOM when the editor is destroyed - see attached tableresize_destroy.gif.

[Piotrek Koszuliński]

I haven't yet checked this TC, but it seems to be very likely given the changes in 4.3.

[Jakub Ś]

Problem can be reproduced from CKEditor 4.0 beta

[Piotr Jasiun]

I've added code which remove resizer when editor is destroyed. Changes in ​t/11179 and corresponding test branch.

[Piotrek Koszuliński]

1. document.find() could be used in tests instead of checking all divs.
2. There's a code style issue in tests (missing semicolon after count++).
3. Tests are not executed in strict mode.
4. Why do you add stylesheetparser and wysiwygarea plugins in tests?

[Piotr Jasiun]

Replying to Reinmar:

1. document.find() could be used in tests instead of checking all divs.

You're right. I thought that attribute selectors are not supported in IE8, but it looks they work pretty well.

3. Tests are not executed in strict mode.

Added.

4. Why do you add stylesheetparser and wysiwygarea plugins in tests?

Because these tests does not work in without it.

[Piotr Jasiun]

• ​git:ab49df9
• tests:b9f79a8