- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Jan 2018 12:08:54 +0000
- To: public-device-apis-log@w3.org
@kenchris, the extensibility story recommended by the spec has been to extend `SensorOptions`, see https://w3c.github.io/sensors/#example-webidl I think we could make returning of the applied attributes a new Level 2 feature and/or try to resolve it as part of #63. What comes to the naming coord(s) vs. coordinate(s). There's some precedence for both: https://html.spec.whatwg.org/#dom-a-coords https://html.spec.whatwg.org/#attr-area-coords https://dev.w3.org/geo/api/spec-source.html#coords https://dev.w3.org/geo/api/spec-source.html#coordinates_interface I tend to feel spelling out `coordinateSystem` would be better: * Although attribute names and dictionary member names tend to be short and concise, there are longer names in use than that. * Longer form avoids confusion with the short plural form `coords` i.e. no `coordsSystem` typo opportunity. * This is not `getElementById` or `getElementsByTagName` that gets typed 10s of times per app :-) -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/sensors/issues/257#issuecomment-358948370 using your GitHub account
Received on Friday, 19 January 2018 12:08:58 UTC