[bisq-network/bisq] Error messages under input fields are not updated (#5005)

[Jakub Loucký]

### Description

As user types into a validated text field, if the new string is still invalid but the error message (reason of invalidity) changed,
the message is not updated to reflect the new reason.

#### Version

c52d6691

### Steps to reproduce

1. DAO -> Governance->Make Proposal->Proposal for changing a parameter
2. Select BTC maker fee
3. While the current value is 0.001, gradually type `0.0011`. Notice the error messages displayed for each partially entered value.

### Expected behaviour

The error message reflects the reason why the value in the text field is invalid.

E.g.: going from **0.00** to **0.001** should switch from "_dust limit not allowed_" to "_must be different from current value_".

### Actual behaviour

The first error message that "snaps in" and is not updated when the reason for invalidity changes. One of the ways to get a correct message is to focus out of the field and then refocus the field again.

### Screenshots

Below are the states of a field as the value `0.0011` is being entered, and then cleared again.
![instant-error-message-update BEFORE](https://user-images.githubusercontent.com/16313562/103141490-37adc900-46f5-11eb-8495-62315d33f049.png)


#### Device or machine

Windows 10, OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.9.1+1)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/5005
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201225/b65b10b8/attachment.htm>