Block invalid EOS Account characters from being entered within Destination Account field

[stephenpdeos]

Within the EVM Bridge Frontend, the Destination Account field for Withdrawal functions allows input of characters that fall outside the limited criteria for EOS Accounts of

• Must contain exactly 12 characters from the base32 set: ., 1-5, a-z
• Must not end in a dot . character

As a result, we should limit the Destination Account field to

• Accept only the valid range of characters
• Allow input of no more than 12 characters
• Prevents inputting . as the 12th character

[yarkinwho]

There's one corner case can cause trouble: what if I paste in a wrong address. If I block the input, this will significantly confuse user as he may think there's something wrong with the copy/paste mechanism (either blame the site or system).

We need a well designed interaction (such as an extra error message) to counter this case.

In addition, it might be more helpful for a user to identify the problem if the illegal character is shown. That's similar to why you need the display password feature in some cases.

For example, if ii copy a string from my console, if i am not careful enough, i will actually copy the color code as well. then when you paste you will get things like: ^[[200username.

It will be quite confusion why the pasted username cannot go through if i can not see what I actually pasted in.

Therefore, I think we need some careful design before we can push this issue.