I am torn on this. On one hand, the binding user is already aware of the
failure condition since they reported it. We don't invoke the error handler
when e.g. the binding user explicitly closes the binding.

On the other hand, ReportBadMessage is effectively a form of validation
failure, and all validation failures should invoke the error handler.

Leaning towards changing the behavior as proposed, under the condition that
the error handler be invoked asynchronously by the binding object in this
case.

Hi, Ken.

Given it is an explicit action by the binding user which guarantees to close the Binding object, I slightly lean towards keeping the current behavior, and documenting it more clearly.

I feel that it is a little different from other standard validation errors in that the standard errors are automatically handled, without an action from the user. So we need a way to notify the user in that case.

WDYT? Thanks!

Since this argument hasn't come up again, closing the ticket and will reopen the discussion if necessary.