W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2009

Re: DOMTimeStamp interface not defined in L3 events...

From: Doug Schepers <schepers@w3.org>
Date: Mon, 05 Oct 2009 12:40:45 -0700
Message-ID: <4ACA4BBD.6040809@w3.org>
To: www-dom@w3.org
Hi, Folks-

Olli Pettay wrote (on 10/5/09 12:29 PM):
> On 10/5/09 9:07 PM, Jonas Sicking wrote:
>> On Mon, Oct 5, 2009 at 2:10 AM, Olli Pettay<Olli.Pettay@helsinki.fi>

>>> It is always possible to implement the feature by returning 0.
>>> Both D2E and D3E allow that.
>>
>> That seems very strange to me.
> Yeah, that is very strange.

That's a polite assessment.


> Optional features don't really have a
>> good track record. Is there a reason to believe that sites won't
>> depend on this feature if it's available in one or two popular
>> browsers? Unless the feature is so useless that no-one will use it,
>> but in that case it seems better to just remove it.
>>
>> / Jonas
>>
>>
> A real usecase for timestamps would be great.
> Otherwise we could deprecate them and browsers could make .timeStamp
> no-op which has always value 0.

What about syncing between 2 instantiations on 2 different browsers for, 
say, a shared whiteboard.

Maybe I'm being dense, but why can't browsers get the system clock time?

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Monday, 5 October 2009 19:40:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:03 GMT