Added priority to directive

[orzilca]

Fixes various problems causing the editor not to show up or not to respond to ng-model change

[karthikbalu]

This is a very high priority fix and worked for me after hours of pain, can u please merge it ASAP pls
Thanks

[paivaric]

Please.. merge this... i need this too... tks!!!

[ryanberckmans]

This PR fixed my issue. I had ng-model="some.object.property"; model updates weren't calling ngModel.$render, so the editor wasn't synced with the model; I set priority: 999,; now it works.

[deeg]

I hate to set an arbitrary priority for no reason. So far I have not found any instances where a priority helped me.

Do you think you could post a Plunker or FIddle demonstrating the issue? If it is really fixing issues for many people I don't mind getting it into the next release, I just want to make sure we have some reason for it.

[AGiorgetti]

Looking at the Angular code I'm pretty sure the problem is in redefining 'ngModel.$render' and the order of execution of the directives.
Assuming you have no priority uiTinymce will run with the same priority as angular 'textarea' directive (which is defined by the 'inputDirective' variable, just look in the Angular code).
The linking function of this angular directive is redefining the ngModel.$render function too, and this can sometimes override uiTinymce $render function (no execution order guaranteed with directive of the same priority).
The code I'm talking about is at this link:
https://github.com/angular/angular.js/blob/40c974ab148cdbb80bd0f470f0ebf70f0fb228d4/src/ng/directive/input.js#L1171

[fabian]

Here's a Plunker showing the issue: http://plnkr.co/edit/gxnnI1IuJv8aFjgPGPcs

[deeg]

@fabian, thanks for posting the plunker.

I added priority with 999 for now, but I might change to a lower number if I hear it causes issues for people.