Set contenteditable=false on editor destroy() when enableContentEditable is true

[mattleff]

This complements the behavior on editor creation.

[ipeychev]

Hey @mattleff,

Thank you for the contribution! This PR looks good, some note about the commit rules we have:

1. Each commit should be associated with an issue. We do that by adding Fixes #xxx in the commit message. In this case we can track any comments related to the issue, etc.
2. The commits should have tests, except if technically impossible. We do have tests for destroying the editor, you may add another one which covers the change in your PR.

Thanks again for the contribution!

Iliyan

[ipeychev]

Just started reviewing :)

Sent from GH.

[ipeychev]

Thank you, pull request merged! See changes here.

Sent from GH.

[ipeychev]

Okay, I added the needed tests, but please the next time send us PR with tests. If you don't know how to do them, feel free to ask for help.

Thanks,

[mattleff]

@ipeychev Sorry I hadn't had a chance to work on unit tests! Do you have a page that explains how to run the unit tests? I have a couple more pulls I'd like to send and I can do the unit tests if I know how.

[ipeychev]

Hey @mattleff,

The tests we run simple with with gulp test. I have on my machine (Mac) installed VMs for all the supported IE versions. I used ievms to install them.

Hope that helps!