Introduction

A proposed <geolocation> element would let pages request location in a standard, permission-aware way—reducing custom JS and improving consistency with browser privacy UIs. We look at the current spec and polyfill options.

How It’s Designed

Declarative and permission-first The element is designed to align with browser prompts and settings, so users get a clear “this site wants location” experience without script-heavy workarounds.

Attributes and behavior We cover proposed attributes for accuracy, timeout, and fallbacks, and how they map to the existing Geolocation API so you can plan ahead.

Use Cases and Status

Maps, local search, and “near me” features are the obvious fits. We discuss implementation status, fallbacks for older browsers, and how this fits with privacy-first browser capability changes.