-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow first bech32 character to be uppercase? #25
Comments
@dermoth Interesting observation, but it does seem very platform specific - so perhaps it's better to deal with it specifically there? |
Yes and no... suppose I have a web-based application that takes an address for input, this is not platform-specifc per se, but then if I use my mobile browser on it and it capitalizes the address it may fail. Similarly, I could enter the address in an email and the client could auto-corect it by capitalizing the first letter... then once copy-pasted into an application it would fail. |
@dermoth the interface should disable auto capitalization? |
@dermoth I don't expect this to be a big problem, and even in the cases where it is, I'd rather be overly cautious - if user interfaces modify input in some ways, we can't prevent them from modifying them in other ways too, which are perhaps more of an issue. |
While I understand why Bech requires all upper or lower characters, I think the standard should still permit the first character to be uppercase as many mobile input devices will automatically make it so.
Explicitly allowing so in the standard will avoid developers from having to choose between usability and correctness. It also reduce the risk of having non-standard applications create confusion amongst users.
The text was updated successfully, but these errors were encountered: