4 ms·

I'm sorry to say this is everything I hate about "modern" UI. It looks fantastic, but, for example, the YYYY/MM/DD field, I can't just write 19/2/23 or whateve

I'm sorry to say this is everything I hate about "modern" UI. It looks fantastic, but, for example, the YYYY/MM/DD field, I can't just write 19/2/23 or whatever (explicitly entering the delimiting slashes), I have to follow the prescribed format, 2019/02/23 (oh, ok thankfully 2 gets filled to 02 automatically). Try 1/20 in the MM/YY field. Doesn't work. It seems fairly simple to fix; when the user types a delimeter, trust them.

deleted 8y ago
[deleted]
thegeomaster 8y ago
Yep, I encountered the same issue and became frustrated within seconds. From a user's perspective: I'm trying to enter a character which makes perfect sense in context, but the key press is ignored. There's no reason to restrict the user's actions in such a way.
leeoniya 8y ago
> Try 1/20 in the MM/YY field. Doesn't work. i've never seen a card that specified expiration month with a single digit. google images for "card expiration" does not bring up any examples either. a placeholder="MM/YY" should make it clear that both are needed.
- teknopaul 8y ago
  FYI Firefox mobile was unable to enter dates in January. I agree this is bad practice. I have similar code in an app I'm writing right now, I also didn't consider the usability issues or wierd delete cases. Gonna remove the code after reading this thread. Falls under trying to be clever. I think slightly increasing the space between groups of numbers might be acceptable? Anything that magically inserts characters seems to be problematic.
- jeroenhd 8y ago
  To humans, 01 is the same as 1. To computers, there's two integers separated by a slash. While it's true that there's a leading 0 on the card itself, there's no reason not to just split on the / and convert both sides to integers.
  - satokema 8y ago
    It depends on the human. Some humans might interpret "01" as one yes, but others will see it as a "zero-one".
- gumby 8y ago
  yes, but this is what people write when filling out paper forms, showing that they consider 0 suppression the norm.
mintplant 8y ago
> I can't just write 19/2/23 or whatever (explicitly entering the delimiting slashes), I have to follow the prescribed format, 2019/02/23 I think this is exactly the point: to guide users toward inputting data in a standard format.
- mch82 8y ago
  Yes, that is the point
- jacknews 8y ago
  I would say it's forcing users to follow the exact format, not guiding them. But then why does 2019/2/24 get automatically expanded to 2019/02/24 (adding the leading zero to the month), but not 19/2/24? As I said, it should be a fairly simple change to respond to delimiters, and marshal the input into the required format without forcing the user to slavishly follow the exact prescription. But if the intent is to do that, then it's a trend I do not agree with at all.

deleted 8y ago

[deleted]

thegeomaster 8y ago

Yep, I encountered the same issue and became frustrated within seconds. From a user's perspective: I'm trying to enter a character which makes perfect sense in context, but the key press is ignored. There's no reason to restrict the user's actions in such a way.

leeoniya 8y ago

> Try 1/20 in the MM/YY field. Doesn't work. i've never seen a card that specified expiration month with a single digit. google images for "card expiration" does not bring up any examples either. a placeholder="MM/YY" should make it clear that both are needed.

teknopaul 8y ago
FYI Firefox mobile was unable to enter dates in January. I agree this is bad practice. I have similar code in an app I'm writing right now, I also didn't consider the usability issues or wierd delete cases. Gonna remove the code after reading this thread. Falls under trying to be clever. I think slightly increasing the space between groups of numbers might be acceptable? Anything that magically inserts characters seems to be problematic.
jeroenhd 8y ago
To humans, 01 is the same as 1. To computers, there's two integers separated by a slash. While it's true that there's a leading 0 on the card itself, there's no reason not to just split on the / and convert both sides to integers.
- satokema 8y ago
  It depends on the human. Some humans might interpret "01" as one yes, but others will see it as a "zero-one".
gumby 8y ago
yes, but this is what people write when filling out paper forms, showing that they consider 0 suppression the norm.

mintplant 8y ago

> I can't just write 19/2/23 or whatever (explicitly entering the delimiting slashes), I have to follow the prescribed format, 2019/02/23 I think this is exactly the point: to guide users toward inputting data in a standard format.

mch82 8y ago
Yes, that is the point
jacknews 8y ago
I would say it's forcing users to follow the exact format, not guiding them. But then why does 2019/2/24 get automatically expanded to 2019/02/24 (adding the leading zero to the month), but not 19/2/24? As I said, it should be a fairly simple change to respond to delimiters, and marshal the input into the required format without forcing the user to slavishly follow the exact prescription. But if the intent is to do that, then it's a trend I do not agree with at all.