On Wed, 6 Apr 2011, Andrew de Andrade wrote:
Depending on the browser and device, permission will be asked either in
a bar across the top of the browser (Firefox and Chrome on the desktop)
or with a modal dialog (Safari on the desktop and on the iPhone). [...]
As the creator of a site
Biju wrote:
What I want from browser vendors is make
navigator.geolocation.getCurrentPosition
and navigator.geolocation.watchPosition ONLY callable from a CLICK event.
I thought we all learned lesson from window.open popups
window.open is still entirely underspecified in standards when it
I'm building a web-app that makes use of the Geolocation API. While
building my application, I've come across an issue with how browser
makers have implemented the Geolocation API.
Depending on the browser and device, permission will be asked either
in a bar across the top of the browser (Firefox
On Wed, Apr 6, 2011 at 4:37 PM, Andrew de Andrade
and...@deandrade.com.brwrote:
2) The HTML5 specification defines how browsers should implement this
consistently -- either a bar across the top OR modal dialog box, but
not both. This isn't ideal either since there are arguments both for
and
On Wed, Apr 6, 2011 at 8:04 PM, Peter Kasting pkast...@google.com wrote:
Furthermore, modal
dialogs have other usability issues that the browser vendor may wish to
avoid, e.g. requiring script on many different tabs to stop.
Are you thinking of how the prompt, etc. require that the UA pause
On Wed, Apr 6, 2011 at 7:37 PM, Andrew de Andrade
and...@deandrade.com.br wrote:
2) The HTML5 specification defines how browsers should implement this
consistently -- either a bar across the top OR modal dialog box, but
not both. This isn't ideal either since there are arguments both for
Right
