I ran across this seemingly unresolved issue with the caret moving to the beginning of a contenteditable DOM node when re-rendered via a custon #angularjs
directive. The author's issues seem to happen when he applies two directives to one element, one for valid input only and the other for bidirectional communication between the view and model for #contenteditable
elements. Either way, I'm glad I ran across this post, because his contenteditable directive works without the caret issues I was having.