This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17762 - lastModifiedDate should not be nullable
Summary: lastModifiedDate should not be nullable
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: File API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Arun
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-12 16:47 UTC by Arun
Modified: 2012-08-17 21:15 UTC (History)
2 users (show)

See Also:

Attachments

Description Arun 2012-07-12 16:47:02 UTC 
We should specify a non-null and arbitrary return value that is returned when the mdate cannnot be determined.

Possible suggestions include arbitrary dates in the past that are unlikely.
Comment 1 Anne 2012-07-12 16:55:42 UTC 
Just do the same as: http://www.whatwg.org/specs/web-apps/current-work/#dom-document-lastmodified (current date and time)
Comment 2 Arun 2012-08-17 21:15:41 UTC 
Done.

http://dev.w3.org/2006/webapi/FileAPI/#dfn-lastModifiedDate

Reopen if necessary.