Date entry autocomplete not helpful
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTG |
Fix Released
|
High
|
Kevin Mehall |
Bug Description
A couple of problems with the way the text boxes beside "Starting on" and "Due for" handle dates typed manually (as opposed to entered using the calendar).
1 — the date format does not match that used in the tasks list. Dates are shown as, e.g. "2009/12/03" instead of "2009-12-03" on my system.
2 — the entry is too eager to parse entries. For example, in typing "2009-11-30", the following happens after "2009-11-3" is typed:
* Red background denoting an invalid date disappears.
* Entry contents are replaced with "2009/11/03"
* Cursor is returned to the beginning of the entry.
Consequently, when the final "0" is typed, it results in the value "02009/11/03" being displayed, and the entry automatically removes the leading zero.
The same process can be observed when using the date format the entry seems to prefer; i.e. starting with "2009/11/03" and attempting to use Backspace to remove the last two characters and then type "30" is impossible.
I am of the opinion that parsing of the contents of the entry should happen only if a user presses Enter, but in any case the current behaviour is frustrating.
Changed in gtg: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in gtg: | |
assignee: | nobody → Kevin Mehall (kevin-mehall) |
status: | Confirmed → Fix Committed |
Changed in gtg: | |
status: | Fix Committed → Fix Released |
will investigate that for 0.2 and report it to 0.3 if no time. This is not a release blocking bug.