W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2014

[vibration] issue status summary

From: <Frederick.Hirsch@nokia.com>
Date: Fri, 3 Jan 2014 20:35:56 +0000
To: <public-device-apis@w3.org>
CC: <Frederick.Hirsch@nokia.com>
Message-ID: <3FDDC26F-C806-4BAC-AB28-2314A0D9DBEA@nokia.com>
I took action to review status of Vibration API issues in tracker. I've updated the ISSUEs, summary is here:

(1) ISSUE-146 : Add vibration strength control ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/146 

Status: Postponed until implementation support, v.next; changed status of Issue from Open to Postponed. (all postponed items in tracker mean postponed until v.next)

WG resolved  to postpone 3 Oct 2013, http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/att-0024/minutes-2013-10-03.html#item04

(2) ISSUE-149 : handling of long vibration list - truncate or no vibration at all ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/149 

Open - proposed resolution agreed but not incorporated into specification

WG agreed resolution on 10 October 2013, http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/att-0128/minutes-2013-10-10.html#item04

RESOLUTION: Adopt proposal as in http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0012.html, adding Note that implementation may break into multiple pieces if list too long , potential concern if best effort does not meet application expectations

Did not update spec asking for implementer feedback - http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0112.html

Did not receive any additional information, suggest we now update spec as proposed, to close issue

(3) ISSUE-150 : Should vibration be additive when multiple instances, e.g. iframes ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/150 

Status: resolved, closed.

Resolved,  10 October 2013, http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/att-0128/minutes-2013-10-10.html#item04

RESOLUTION: Adopt proposal associated with ACTION-652: http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0003.html

Implemented in editors draft but not in CR draft (it seems the limitation to browsing context may require a new LC?)

CR draft out of sync with editors draft.

(4) ISSUE-156 : add the [Clamp] attribute to the argument of the vibrate method ; on [Vibration API] http://www.w3.org/2009/dap/track/issues/156 

Status: Postponed until stable WebIDL specification with agreed [Clamp] attribute is available. ; changed status of Issue from Open to Postponed.

http://lists.w3.org/Archives/Public/public-device-apis/2013Nov/0001.html

regards, Frederick

Frederick Hirsch
Nokia

For Tracker, this should complete ACTION-672
Received on Friday, 3 January 2014 20:40:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:03 UTC