Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Geolocation API doesn't work with sandboxed iframes or provide an error

sstewartgallus
sstewartgallus
more options

The navigator.geolocation.watchPosition function call doesn't work with sandboxed iframes where allow-same-origin is not specified (so the iframe counts as a unique and anonymous origin). I guess that making the sandboxed iframe not inherit the permission to use the the geolocation API of the site that contains is a sensible decision. Personally, I would like to have some way of creating sandboxed iframes that can also use the geolocation API but I can understand if that is not implemented. However, a sandboxed iframe also does not receive a permission error when it uses the geolocation API which is completely wrong and makes the situation really hard to debug.

Perhaps, the bug at https://bugzilla.mozilla.org/show_bug.cgi?id=675533 is related somehow?

The navigator.geolocation.watchPosition function call doesn't work with sandboxed iframes where allow-same-origin is not specified (so the iframe counts as a unique and anonymous origin). I guess that making the sandboxed iframe not inherit the permission to use the the geolocation API of the site that contains is a sensible decision. Personally, I would like to have some way of creating sandboxed iframes that can also use the geolocation API but I can understand if that is not implemented. However, a sandboxed iframe also does not receive a permission error when it uses the geolocation API which is completely wrong and makes the situation really hard to debug. Perhaps, the bug at https://bugzilla.mozilla.org/show_bug.cgi?id=675533 is related somehow?

Izabrano rješenje

I think this is beyond the scope of support. You might want to file a new bug and see how that goes: https://bugzilla.mozilla.org/

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Odabrano rješenje

I think this is beyond the scope of support. You might want to file a new bug and see how that goes: https://bugzilla.mozilla.org/