On setup, sets form as pristine

[cdhowie]

This line sets the form containing a tinymce directive as pristine when the editor is configured. I'm not sure why this is necessary, but it makes it unnecessarily convoluted to dynamically create new editors. Any new editor that is created will mark the whole form as pristine, even if a totally different component (not even a tinymce editor) was dirty at the time.

This can be worked around by nesting the editor in a <div ng-form>, giving it its own form controller that it can mess with as it pleases.