diff options
| author | Frédéric Brière <fbriere@fbriere.net> | 2020-03-31 17:24:27 -0400 |
|---|---|---|
| committer | Frédéric Brière <fbriere@fbriere.net> | 2020-03-31 18:04:14 -0400 |
| commit | ba8292d0fb08d39b0d8b9913889ffd589821b070 (patch) | |
| tree | 8f70c3fe70e9f7026a1aa8bf74f6aec6667e5b31 /NEWS | |
| parent | ea00ce2f9d24ade8bcf8736a31516b41511e6233 (diff) | |
| download | twinkle-ba8292d0fb08d39b0d8b9913889ffd589821b070.tar twinkle-ba8292d0fb08d39b0d8b9913889ffd589821b070.tar.gz twinkle-ba8292d0fb08d39b0d8b9913889ffd589821b070.tar.lz twinkle-ba8292d0fb08d39b0d8b9913889ffd589821b070.tar.xz twinkle-ba8292d0fb08d39b0d8b9913889ffd589821b070.zip | |
Relax GetProfileNameForm validator to only check individual characters
QRegExpValidator can be somewhat user-unfriendly, as it will prevent
characters from being input, or even deleted, while leaving the user in
the dark as to what is going on.
Retricting the set of characters allowed shouldn't pose a problem if we
make a mention of this on the form. Checking for a leading "." or "@",
however, is better left at submission time, with an explicit error
message in that case.
Diffstat (limited to 'NEWS')
0 files changed, 0 insertions, 0 deletions