ngMessage and ngBind do not work together

[43081j]

If you have a custom validation key (such as server in this case), and try bind the ngMessage element to some object you presumably have the error message in, it does not work.

<div ng-if="myForm.test.$dirty" ng-messages="myForm.test.$error">
    <span ng-message="server" ng-bind="errors.test"></span>
</div>

The above does not work, the span remains empty but visible and errors.test is indeed populated (and visible in scope, by trying angular.element($0).errors.test).

If you use a child, like so:

<span ng-message="server">
    <span ng-bind="errors.test"></span>
</span>

This works correctly.

Is this expected functionality or a bug? I have no issue with having to use a child if it is expected to behave this way.

Example here.

[jamesbrobb]

Just came across this issue as well, is there any update/progress on it? Thanks.

[OliverKK]

Same here. Any news on this?

[matsko]

This should work now in 1.4. But you need to use ngRepeat.

[matsko]

c9a4421

[vedraan]

Note that it also works like this: <span ng-message="server">{{errors.test}}</span>

[matsko]

Closing this for now since it is working in 1.4.

[parliament718]

I'm experiencing this bug in 1.4.7

[Narretz]

It seems like ng-message + ng-bind was never actually solved. It really doesn't work in 1.4.7: http://plnkr.co/edit/bubtiS5bULNiCw5ach6Y?p=preview

[yerol]

You can place the message in a separate element inside ng-message until this issue is resolved. As in:

<span ng-message="required">
    <span ng-bind="errors.required"></span>
</span>