- From: Wonsuk Lee <wonsuk11.lee@samsung.com>
- Date: Tue, 03 Sep 2013 15:39:52 +0900
- To: 'Christophe Dumez' <ch.dumez@sta.samsung.com>
- Cc: public-sysapps@w3.org
- Message-id: <083c01cea870$6504f3f0$2f0edbd0$@samsung.com>
Hi. Chris. Thanks for email. +1 for removing timezone support. Kr, Wonsuk. From: Christophe Dumez [mailto:ch.dumez@sta.samsung.com] Sent: Monday, September 02, 2013 5:05 PM To: public-sysapps@w3.org Subject: [web-alarms] Remove timezone support from Task Scheduler API Hi, It was proposed during the last SysApps face to face in Toronto to remove timezone support from the Task Scheduler API [1]. This would essentially mean removing the TimezoneDirective [2] from the API and pass a number of second since epoch to schedule a task instead of an EcmaScript Date (e.g. by using "Date.now() + n"). The change was proposed for several reasons: - The TimezoneDirective is not very clear, may be confusing to the developers and makes the API more complex, - The current timezone support is not sufficient to handle calendar use cases anyway since you cannot explicitly specify which timezone to use, - The Date object may be removed from Web IDL [3] as its use was discouraged on es-discuss [4]. I am sending this message to the mailing list to gather broader feedback before updating the specification draft. Please let us know how you feel about this change. [1] http://www.w3.org/2012/sysapps/web-alarms/ [2] http://www.w3.org/2012/sysapps/web-alarms/#timezonedirective [3] https://www.w3.org/Bugs/Public/show_bug.cgi?id=22824 [4] http://esdiscuss.org/topic/frozen-date-objects Kr, -- Christophe Dumez - Samsung Telecommunications America
Received on Tuesday, 3 September 2013 06:40:28 UTC