- From: Marta Pawlowska <m.pawlowska@samsung.com>
- Date: Tue, 03 Sep 2013 11:01:51 +0200
- To: 'Christophe Dumez' <ch.dumez@sta.samsung.com>, public-sysapps@w3.org
- Message-id: <01c001cea884$3b1bcc30$b1536490$%pawlowska@samsung.com>
Hi Chris, +1 for removing TimezoneDirective Best regards, Marta From: Christophe Dumez [mailto:ch.dumez@sta.samsung.com] Sent: Monday, September 02, 2013 10:05 AM 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 09:02:26 UTC