- From: Arun Ranganathan <aranganathan@mozilla.com>
- Date: Thu, 11 Nov 2010 08:33:04 -0800 (PST)
- To: "Tab Atkins Jr." <jackalmage@gmail.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>, Anne van Kesteren <annevk@opera.com>
----- Original Message ----- > On Thu, Nov 11, 2010 at 1:28 AM, Anne van Kesteren <annevk@opera.com> > wrote: > > On Thu, 11 Nov 2010 08:43:21 +0100, Arun Ranganathan > > <aranganathan@mozilla.com> wrote: > >> > >> Jian Li is right. I'm fixing this in the editor's draft. > > > > Why does lastModified even return a DOMString? Can it not just > > return a > > Date? That seems much nicer. > > Probably because WebIDL doesn't (didn't?) have a date type. That's a > silly reason in the first place, and heycam is fixing (has fixed?) it > in the second place. 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. -- A*
Received on Thursday, 11 November 2010 16:33:39 UTC