- From: Rob Manson <roBman@buildAR.com>
- Date: Tue, 25 Mar 2014 06:16:10 +1100
- To: Michael van Ouwerkerk <mvanouwerkerk@google.com>
- CC: public-geolocation <public-geolocation@w3.org>
Hi Michael,
> Hi Rob, that's a nice demo, thanks for sharing. Some replies inline.
Thanks.
> Afaik there is not currently a faster way to these settings on Chrome on
> Android (I work on this project). On desktop, there is an icon inside
> the url bar that gives one-click access to these settings. The most
> obvious challenge here is that there is so little screen real estate on
> mobile devices, so some things are behind more clicks.
Yeah screen real estate is a real challenge. I really like this granular
level of control you've implemented though 8)
> You could file bugs for these browsers. You'll probably get a more
> focused discussion that way.
Will do.
> That sounds like a bug to me. The spec is quite clear: "If the attempt
> fails, the errorCallback must be invoked with a new PositionError
> object, reflecting the reason for the failure."
>
> And the attributes of the PositionError interface are not optional:
>
> [NoInterfaceObject]
> interface PositionError {
> const unsigned short PERMISSION_DENIED = 1;
> const unsigned short POSITION_UNAVAILABLE = 2;
> const unsigned short TIMEOUT = 3;
> readonly attribute unsigned short code;
> readonly attribute DOMString message;
> };
>
> The best way to get this fixed is to file bugs with the relevant projects.
Yeah that's pretty clear then. We'll isolate this issue then raise bugs.
Thanks.
roBman
Received on Monday, 24 March 2014 19:16:37 UTC