Default option "absolute" in addition to 'blank', 'now', or 'relative'

Moving D5 feature requests that aren't going to get into the initial official 5.2 release to be D6 feature requests that could potentially be backported to D5.2.

subscribing

Anyone already working on this?

subscribing +10

btw, the use of relative with a constant sfrtotime value would already be a turn around.
but it unfortunately does not work.

subscribing.

"Common sense" and yes, it should at least work with strtotime (something like '1 January 1990'), but it doesn't.

Subscribing. Has anyone figured out why a valid date string doesn't work?

Subscribing and +1. On the site I'm building now, which is a conference site with specific dates, this would be very useful...

Duplicate of #319195: Set default value to a custom strtotime string (for relative or exact dates)

I don't consider this issue a duplicate at all. That thread talks about a more advanced way to specify the relative value, which is not what is being discussed here. Allow me to cite a specific example.

I'm currently working on a site for a fair which runs for 10 days. I would like the date value to default to the start time of the fair, so that if you are adding a new event you always begin within the fair's run, regardless of when the event is being entered (could be anywhere from 6 months to two weeks before the start of the fair).

The third choice being discussed in that thread is still relative to the time of entry, not the fixed date date option being requested here.

@surge_martin:
Yes, I see your point, and it is a valid one.

But, rather than duplicate, I think these two issues should be merged, providing a simpler, more elegant, & more robust solution for both issues (killing two birds with one stone).
Both issues could be solved if we changed the choices to only two:
'blank' or 'enter a date string'

That 'date string' could be any valid strtotime string like:
now
now + 1 week
Last Thursday
July 10, 2010 <- this is an exact date just like what you want.

So, that is my reasoning and why I think this should be considered as a duplicate of that issue.
What do you think?

If you would update the title of the other issue to acknowledge that accepting a specific date (as part of support for an arbitrary date string) is one of the goals of the feature request, then I will absolutely agree that the two issues can be merged.

Just want to make sure we don't lose track of the actual intent here.

Deal :-) #319195: Set default value to a custom strtotime string (for relative or exact dates)

Thanks for the input.