Description Mickael Istria 2017-07-27 04:33:11 EDT

Forked from Kalyan's discovery and analysis on bug 520205.

With ability to define content-type manually (bug 500892) and to associate editors with content-type (bug 519815), the following -new- workflow is broken:

1. Create a new content-type
2. Associate content-type with an unknown extension such as .lol
3. Associate this content-type with whatever editor (internal or external)
4. Create a new .lol file -> it opens with the specified editor: OK
5. Delete the content-type (directly, do *not* delete associations first)
6. Create a new .lol file: KO
   EXPECTED: it opens with the default system editor (or whatever editor specified by the unknownEditorStrategy)
   GOT: It opens with the previously defined editor

As noticed by Kalyan in bug 520205 comment 7
"""
Even after I delete the newly added content type, The association with the External Editor still exists. This association needs to be deleted once the content type is deleted
"""