Discover the new way to request user location data.

Chrome's platform is a leading web browser developed by Google, offering insights into web standards, browser features, and web development tools. Through documentation, developer tools, and webinars, Chrome provides insights into building modern web applications and optimizing performance. Developers can learn about web APIs, progressive web apps (PWAs), and Chrome DevTools to create fast, secure, and user-friendly web experiences.

Chrome Developers

Chrome 144 introduces the `<geolocation>` HTML element, a declarative alternative to the JavaScript Geolocation API. This element requires user interaction (clicking a button) to request location data, reducing accidental blocks and browser interventions. It evolved from a generic `<permission>` element after origin trial feedback showed improved user trust and success rates. The element simplifies implementation by handling permission states automatically, supports attributes like `autolocate` and `watch`, and includes styling constraints to prevent deceptive patterns. A polyfill and progressive enhancement strategies ensure backward compatibility with browsers that don't support the new element.

Introducing the <geolocation> HTML element

From generic <permission> to specific <geolocation>

If they are adding <code>&lt;geolocation&gt;</code>. They will definitely add <code>&lt;if condition=&quot;checkConditon()&quot;&gt;&lt;/if&gt;</code> <code>&lt;else&gt;&lt;/else&gt;</code> soon. Now CSS also have if else only HTML is left.

Ohh nice to know. Thanks for sharing.

really? WOW after the addition of the “if-else” to CSS this? it’s awesome

What am I missing? Why don’t we update the geolocation API to allow reprompt of permissions OR have browsers remove this ability to snooze sessions or add additional UI?