Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Learn More

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

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?

Ñemoĩporã poravopyre

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/

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0

Opaite Mbohovái (1)

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

Ñemoĩporã poravopyre

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/