Yes, that would solve my problem.<br><br>Theoretically, permission could change between checking and calling getCurrentLocation, but if I'm calling them in the same tick, ocurrence should be vastly rarer than geolocation failures.<br><br><span style="font-family:Prelude, Verdana, san-serif;"><br><br></span><span id="signature"><div style="font-family: arial, sans-serif; font-size: 12px;color: #999999">-- Sent from my HP TouchPad</div></span><span style="color:navy; font-family:Prelude, Verdana, san-serif; "><hr align="left" style="width:75%">On May 5, 2014 11:25 AM, Marcos Caceres &lt;w3c@marcosc.com&gt; wrote: <br></span>
<br>
<br>On May 3, 2014 at 12:56:12 AM, Doug Reeder (reeder_29@yahoo.com) wrote:
<br>&gt; &gt; I do, in fact, persistently store a preference "tag new notes  
<br>&gt; with location". It's undefined initially. If the user sets it  
<br>&gt; true, my app immediately calls the geolocation API to trigger  
<br>&gt; the permission dialog. If the user approves, we're on the happy  
<br>&gt; path. If the user denies permission, the preference is set to  
<br>&gt; undefined - the user has expressed conflicting wishes.
<br>&gt;  
<br>&gt; Unfortunately for my situation, if the user allows geolocation  
<br>&gt; once, it says nothing about whether it will be allowed the next  
<br>&gt; time. In Chrome, allowing geolocation is persistent, but in  
<br>&gt; Firefox and Firefox OS it's not persistent unless the user clicks  
<br>&gt; a second control.
<br>
<br>Ok, good to know. Do you think just adding a `geolocation.permission === 'enabled'` or similar would address the use case?&nbsp;
<br>
<br>Also, maybe good if we could move this back to the list?&nbsp;