List of comments on “Vibration API” (dated 2 February 2012)

Status: allopen proposal pending resolved_yes resolved_no resolved_partial other Type: allsubstantive editorial typo question general comment undefined

Quick access to LC-2602

Comment LC-2602

Commenter: Dominique Hazael-Massieux <dom@w3.org> (archived message)

Context: 3. Vibration Interface Navigator implements Vibration; A...

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Anssi Kostiainen

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

Hi,

The LC WD of the vibration API uses exceptions for cases where the
requested vibration is too long.
http://www.w3.org/TR/2012/WD-vibration-20120202/

But WebIDL has removed support for raising exceptions in its syntax.

In prose, an exception of a particular type can be thrown by
using wording like the following:

Throw a DOMException of type HierarchyRequestError with
message “Cannot append that Node here”.
http://dev.w3.org/2006/webapi/WebIDL/#idl-exceptions

Also, there should be a normative reference to WebIDL.

Dom

Related issues: (space separated ids)

WG Notes: http://lists.w3.org/Archives/Public/public-device-apis/2012Feb/0021.html http://lists.w3.org/Archives/Public/public-device-apis/2012Feb/0028.html

Resolution: ReSpec update: http://lists.w3.org/Archives/Public/public-device-apis/2012Feb/0020.html Added text: "the user agent MAY throw a NotSupportedError exception [DOM4]" and "added a normative reference by adding the usual Web IDL boilerplate to the Conformance section" http://lists.w3.org/Archives/Public/public-device-apis/2012Feb/0022.html

(Please make sure the resolution is adapted for public consumption)