Permissions Policy: geolocation

Support in current browsers

Checked against the current browser versions recorded in MDN browser data 8.1.5.

Browser	Minimum	Outcome	Reason
Chrome	155	Works	Every required mapped BCD feature is available without a recorded qualification.
Edge	154	Works	Every required mapped BCD feature is available without a recorded qualification.
Firefox	157	Not supported	At least one required mapped feature is not available at this browser baseline.
Safari	27	Not supported	At least one required mapped feature is not available at this browser baseline.
Chrome for Android	155	Works	Every required mapped BCD feature is available without a recorded qualification.
Firefox for Android	157	Not supported	At least one required mapped feature is not available at this browser baseline.
Safari on iOS	27	Not supported	At least one required mapped feature is not available at this browser baseline.
Android WebView	155	Works	Every required mapped BCD feature is available without a recorded qualification.
Samsung Internet	30.0	Works	Every required mapped BCD feature is available without a recorded qualification.

The release trace

How support changed

Each segment groups recorded releases with the same result. Gaps between recorded versions are not filled in. This is support at each release, rather than the planner’s check of every release above a minimum.

Chrome

http.headers.Permissions-Policy.geolocation

1 – 8786 recorded releases
Not supported
88 – 15568 recorded releases
Works

Edge

http.headers.Permissions-Policy.geolocation

12 – 8715 recorded releases
Not supported
88 – 15467 recorded releases
Works

Firefox

http.headers.Permissions-Policy.geolocation

1 – 157160 recorded releases
Not supported

Safari

http.headers.Permissions-Policy.geolocation

1 – 2761 recorded releases
Not supported

Chrome for Android

http.headers.Permissions-Policy.geolocation

18 – 8763 recorded releases
Not supported
88 – 15568 recorded releases
Works

Firefox for Android

http.headers.Permissions-Policy.geolocation

4 – 157141 recorded releases
Not supported

Safari on iOS

http.headers.Permissions-Policy.geolocation

1 – 2758 recorded releases
Not supported

Android WebView

http.headers.Permissions-Policy.geolocation

1 – 8758 recorded releases
Not supported
88 – 15568 recorded releases
Works

Samsung Internet

http.headers.Permissions-Policy.geolocation

1.0 – 14.233 recorded releases
Not supported
15.0 – 30.019 recorded releases
Works

BCD 8.1.5 · catalogue 2.3.0. Source corrections can change this trace without a new browser release.

A fixed result snapshot

What those browser runs reported

Reviewed 11 October 2026

These are published results from specific stable-labelled browser builds. They are separate from the compatibility calculation and from evidence about your application. File outcomes and subtest counts stay separate. OK describes a completed harness, which can still contain failing subtests; Pass and Fail can also describe tests without a harness.

Selected directive tests: Geolocation policy violation reports in enforced and report-only modes.

Reporting support, location availability and user permission can affect these outcomes. They do not isolate basic geolocation blocking or cover every frame allowlist.

Counts cover every subtest reported by each selected file, including any setup or complementary cases. They are not isolated directive pass counts or application evidence.

Exact browser builds, systems and source revision

firefox 157.0 · linux 22.04 · stable
Run 4877098740350976 · 2026-10-06T10:36:34.451Z to 2026-10-06T11:50:28.028Z
cc74d2669f5de548e808779877d1d33339ec5115
safari 27.0 (22625.1.29.11.27) · mac 27.0 · stable
Run 5164107446878208 · 2026-10-06T06:14:03.64Z to 2026-10-06T09:13:55.471Z
cc74d2669f5de548e808779877d1d33339ec5115
chrome 154.0.8037.92 · linux 22.04 · stable
Run 6218298311311360 · 2026-10-06T07:44:01.102Z to 2026-10-06T11:57:16.569Z
cc74d2669f5de548e808779877d1d33339ec5115

“Stable” is the upstream run label. Complete runtime flags were not supplied by the summary API. These results do not cover every browser version, mobile platform or operating system.

Geolocation policy reporting

permissions-policy

2 of 2 selected test files have retained results. The parent directory contains 118 retained files from 161 returned search matches. Only the exact files listed below enter these totals.

Browser build	Subtests passed / reported	File outcomes
firefox 157.0	0 / 2	2 Timeout
safari 27.0 (22625.1.29.11.27)	0 / 1	1 Error · 1 Timeout
chrome 154.0.8037.92	1 / 2	2 OK

Read all 2 retained file results

Test file	firefox	safari	chrome
`reporting/geolocation-report-only.https.html`	Timeout · 0/1 subtests	Timeout · 0/1 subtests	OK · 0/1 subtests
`reporting/geolocation-reporting.https.html`	Timeout · 0/1 subtests	Error · 0/0 subtests	OK · 1/1 subtests

Source API query (whole directory)Test source at the run revision

Source-response fingerprint

SHA-256 150245d1d61d5ee8bd787fd2cfb3d5520a0db0965f2af0140d8ba5b382f5489c

The digest identifies the complete downloaded directory response used for this projection, before file selection. It does not authenticate the runner or prove that the results are truthful.

What this feature can and cannot do

Helps protect against

Unexpected capability use
Over-privileged embedded content

Does not guarantee

Application authorisation
User permission decisions
Other capabilities

What you need before using it

An explicit capability and frame allowlist
Review of inherited frame restrictions

Fallback to keep in place

Request only necessary capabilities and provide a usable path when access is denied.

Browser data used

Support can be calculated

http.headers.Permissions-Policy.geolocation

MDN reference

Specifications

w3c.github.io

Support across major browsers

Adoption information available

Web Platform Baseline indicates when a feature became available across major browsers. It does not inspect your website or replace the browser-by-browser result.

Geolocation API

http.headers.Permissions-Policy.geolocation

Status: not Baseline

Public browser tests

Relevant tests found

Geolocation policy violation reports in enforced and report-only modes.

Source reviewed 11 October 2026cc74d2669f5de548e808779877d1d33339ec5115

Geolocation policy reporting
- permissions-policy/reporting/geolocation-report-only.https.htmlreviewed test source latest public results
- permissions-policy/reporting/geolocation-reporting.https.htmlreviewed test source latest public results

Limit:Reporting support, location availability and user permission can affect these outcomes. They do not isolate basic geolocation blocking or cover every frame allowlist.