Re: Inconsistent definition of timeout / maximumAge in Geo v1

On lun., 2014-02-03 at 17:34 +0100, Dominique Hazael-Massieux wrote:
> * the timeout attribute in the PositionOptions interface is defined as
> "long", with a default value of Infinity
> * yet, the "long" type doesn't accept "Infinity" as a valid value
> (more
> specifically, it casts it to "0")

Interestingly, Firefox works around this by setting the default value of
timeout to 0x7fffffff;
http://mxr.mozilla.org/mozilla-central/source/dom/webidl/Geolocation.webidl

I'm still unclear why maximumAge = Infinity doesn't get converted to 0,
though.

Dom

Received on Friday, 14 February 2014 10:04:54 UTC