W3C Geolocation API Errata (original) (raw)
Errata for Geolocation API Second Edition
This section is a place-holder for errata to be published on the W3C Geolocation API Second Edition dated of 8 November 2016.
Currently no errata have been reported.
Errata for Geolocation API First Edition
This section describes the known errata and proposed corrections for the W3C Geolocation API First Edition published as a Recommendation on 24 October 2013.
WebIDL improvements
Given the evolution of WebIDL, the following changes would better match
- the
NavigatorGeolocation
interface would be better expressed as a partial interface; - the prose describe that
timeout
andmaximumAge
inPositionOptions
can take infinite values, butInfinite
gets converted to 0 for values of typelong
; - the interface
PositionOptions
would be better written as a dictionary with default values matching the prose description of 5.2; the said prose can then be reduced
Proposed correction:
- the interface
NavigatorGeolocation
should be rewritten as:
partial interface Navigator {
readonly attribute Geolocation geolocation;
}; - using the
[Clamp]
extended attribute getsInfinite
properly converted to the maximum value of the integer type; - The WebIDL declaration of PositionOptions should be changed to:
dictionary PositionOptions {
boolean enableHighAccuracy = false;
[Clamp] unsigned long timeout = 0xFFFFFFFF;
[Clamp] unsigned long maximumAge = 0;
};
In 5.1, the pre-processing steps ofgetCurrentPosition
and “watch process” are removed. In 5.2, the text describing the default values ofenableHighAccuracy
,timeout
andmaximumAge
(paragraphs 5, 7 and 10 in that section) are removed.
Conformance requirements
- The sentence starting with “Objects implementing the
Navigator
interface” is redundant with WebIDL and can be removed; - the
getCurrentPosition
and “watch process” algorithms are indicated as “should execute the following set of steps”; the steps in the algoritms are in fact mandatory.
Proposed corrections:
- Remove second paragraph of section 5.1
- Replace “should execute” with “must execute” in the
getCurrentPosition
and “watch process” algorithms
References
- The list editors for the [BROWSINGCONTEXT] and [NAVIGATOR] references (linked to HTML5) is incorrect;
- The full stop after the title of the URI spec should be moved before the space;
- Instead of The DOMTimeStamp Type, a more useful reference is the one defined in WebIDL
- RFC3066 is listed in the references, but not used in the specification, and should be removed
Giridhar Mandyam, Chair, Qualcomm Innovation Center
Kazuyuki Ashimura <ashimura@w3.org>, Team Contact, W3C
Revision:1.10Revision: 1.10 Revision:1.10