W3C home > Mailing lists > Public > public-geolocation@w3.org > February 2014

Re: CfC: approve Errata for Geo v1

From: Michael van Ouwerkerk <mvanouwerkerk@google.com>
Date: Wed, 12 Feb 2014 11:38:24 +0000
Message-ID: <CAF40kP6PTK0LLDuG5yvgWY6sEZyMEonjfSvUWtprHev2Xx9tUA@mail.gmail.com>
To: Dominique Hazael-Massieux <dom@w3.org>
Cc: "public-geolocation@w3.org" <public-geolocation@w3.org>
Hi Dom,

I think the timeout member of PositionOptions should not have a default
value. That way, it can be 'not present' to replace the previous use of
Infinity as default.

On re-reading, I noticed that for maximumAge the spec already specifies a
default value of 0, so we actually cannot use the 'not present means
Infinity' trick.

I'd suggest we cannot rephrase step 2 as I suggested earlier, so I withdraw
that suggestion. However, in section 5.2 for the PositionOptions interface
there is this sentence:
"Setting the maximumAge to Infinity must determine the implementation to
return a cached position regardless of its age."

Since it is not possible according to WebIDL to set an integer type to
Infinity, how about just deleting this sentence? Not sure how all browsers
have implemented this. In Chrome, I can specify Infinity in js, and I get a
cached position. In practice, setting a large number is very likely to have
the desired effect. Using the unsigned long type, a maximumAge of nearly 50
days can be specified. If [Clamp] is used, there should be no overflow

What do you think?



On Wed, Feb 12, 2014 at 6:59 AM, Dominique Hazael-Massieux <dom@w3.org>wrote:

> Hi Michael,
> Thanks for your feedback (on this and on the Infinity question); here
> comes attached a new version of the proposed errata that incorporates
> your feedback.
> I will publish them at
> http://www.w3.org/2008/geolocation/geoapi-errata.html next week unless I
> hear otherwise.
> Dom
Received on Wednesday, 12 February 2014 11:38:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:51:07 UTC