Specifically, where a defined policy blocks use of this feature, calls to
watchPosition() will cause those functions'
callbacks to be invoked with a
GeolocationPositionError code of
By default, the Geolocation API can be used within top-level documents and their same-origin child frames. This directive allows or prevents cross-origin frames from accessing geolocation. This includes same-origin frames.
A list of origins for which permission is granted to use the feature. See
Permissions-Policy> Syntax for more details.
The default allowlist for
SecureCorp Inc. wants to disable the Geolocation API within all browsing contexts
except for its own origin and those whose origin is
can do so by delivering the following HTTP response header to define a Permissions Policy:
Permissions-Policy: geolocation=(self "https://example.com")
FastCorp Inc. wants to disable
geolocation for all cross-origin child
frames, except for a specific
<iframe>. It can do so by delivering the following
HTTP response header to define a Permissions Policy:
Then include an allow attribute on the
<iframe src="https://other.com/map" allow="geolocation"></iframe>
allow attributes can selectively enable features in certain frames, and not in others,
even if those frames contain documents from the same origin.
|Geolocation API |
BCD tables only load in the browser