platform-guideline 1 linked patterns checked
MDN Web Docs: Geolocation API
Documents secure-context geolocation access, user permission prompts, current-position and watch-position methods, position and error callbacks, permission lifetime, and privacy-sensitive location data.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Location permission flow | Choose location permission flow when current device coordinates are the central interaction and the task needs permission timing, precision, grant or denial recovery, and location lifecycle states. | The native browser or OS prompt appears only after users understand why location is needed and choose a location-dependent action. | Supports secure-context geolocation, prompts, current or watched position, errors, permission lifetime, and privacy warnings. |
Comparisons supported by this source
- Location permission flow vs permission request vs map view vs address entry vs privacy settings vs offline state
Supports secure-context geolocation, permission prompts, current and watched positions, errors, and permission lifetime.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: MDN Web Docs. Last checked: .