My favorites | Sign in
Project Home Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 10: Show an error for malformed timestamps
2 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ericzh...@google.com


Sign in to add a comment
 
Project Member Reported by ericzh...@google.com, May 4, 2010
What steps will reproduce the problem?
1. Create a narrative or event.
2. In the timestamp field, enter a time without an am/pm designation
3. Look at your living story page.  Everything will fail

What is the expected output? What do you see instead?
A malformed timestamp should generate an error in the compose page rather 
than getting accepted and then totally breaking the page.


May 4, 2010
#1 byjoeyba...@gmail.com
Thanks for isolating this! In a combination of curiosity/irritation/love-of-simplicity: why is it that there is a 
separate, required, time field?
May 4, 2010
Project Member #2 ericzh...@google.com
There's actually already another bug filed about making the timestamp optional, which 
we plan to fix shortly.

The basic reason is: we use the date/time to sort the events in your living story 
page.  We were assuming that you'd always want to put a time down, but it seems that 
many people want to omit it, so we'll default that to 12:00 AM and hide it.
Sign in to add a comment

Powered by Google Project Hosting