As you suggest, there isn’t such a thing as a time field without an assumed date.
Wait: I take that back. Say, for instance, you wanted to track the time-of-day at which something takes place. In that instance, you might want to store a date-less time. In that case, though, storing it as a single-line text field makes as much sense as anything, as it’s ceased to have any relative meaning. If you’re using the value to track how long you spent on a task, though, then there is an assumed date value. Agreed, Airtable doesn’t currently make it as easy as it could be to enter such a value,¹ but I suspect a disembodied time sans date would be more confusing than helpful…
— but that was why I was asking how you would like to see it work, as you evidently have a use case calling for such a feature
- My suggestion would be to treat any two numbers separated by a colon or three numbers separated by two colons as a time, with an optional ‘a’ or ‘p’ for 12-hour clocks, and an assumed date of
TODAY() — but that seemingly might be problematic for some regional uses.