Re: Drop lastPosition from Geolocation?

>
> Note that with my proposal, you can still achieve the availability  
> goal.  Instead of including a position in the error callback, you  
> include an indication that cached data is available, but it was not  
> “fresh” enough.

Are you suggesting that instead of returning position unavailable, we  
add a new error code that expresses the fact that we might have a  
position available but it is outside of the "freshness" that you wanted?