- From: Anne van Kesteren <annevk@opera.com>
- Date: Fri, 12 Nov 2010 12:05:29 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>, "Arun Ranganathan" <aranganathan@mozilla.com>
- Cc: "Eric Uhrhane" <ericu@google.com>, "Web Applications Working Group WG" <public-webapps@w3.org>, "Ian Hickson" <ian@hixie.ch>, public-device-apis <public-device-apis@w3.org>, "Jian Li" <jianli@chromium.org>
On Thu, 11 Nov 2010 17:33:04 +0100, Arun Ranganathan <aranganathan@mozilla.com> wrote: > I agree that a readonly Date object returned for lastModified is one way > to go, but considered it overkill for the feature. If you think a Date > object provides greater utility to simply get at the lastModified data, > I'm entirely amenable to putting that in the editor's draft. It depends on what the use cases are I suppose. But if the last modified date is going to be displayed somehow having a Date object seems more flexible. -- Anne van Kesteren http://annevankesteren.nl/
Received on Friday, 12 November 2010 11:06:21 UTC